openapi: add agent_instructions to MemberNotifyResponse - #411
Merged
Merged
Conversation
Add `repositories` to RumApplicationItem, RumApplicationCreateRequest and
RumApplicationUpdateRequest, backed by a new RumApplicationRepository schema
({repo: "owner/name", subdir}). On update the list is replaced when present,
cleared by an empty array, and left unchanged when omitted.
Drop the flag emoji from the Taiwan SMS region card
…on apps, session and feed fields
The upload script had two ways to leave stale documents in the index: - Full mode upserted every doc but never deleted anything, so pages removed from the repo stayed searchable. - Incremental mode diffed only HEAD~1: a push carrying several commits lost the changes of all but the last one, a renamed file was uploaded under its new path while the old path was never deleted, and a failed or cancelled run dropped its changes for good. Replace both modes with one sync: scan zh/ and en/, list every document id in the index (paginated), upsert all docs, and delete ids that no current file produces. Meilisearch only re-embeds documents whose content changed, so re-uploading unchanged docs is cheap. The run fails without writing anything if the scan is empty or the listing is incomplete. The workflow drops the full_upload input and the fetch depth it no longer needs, and serializes runs per environment so an older sync cannot delete docs a newer one just added. Also strip HTML/MDX tags after joining lines: a tag whose attributes span several lines (e.g. <video>, <Card>) used to survive cleaning. A tag must now start with a letter or '/', so comparisons such as "a < b" and placeholders written in Chinese are kept.
Sync docs to Meilisearch as a full reconcile on every run
…gration-main docs(integration): add New Relic alert setup
docs: AI SRE paid launch
docs: add Aliyun DataWorks Op integration guide
…drill-down contract, cap the Automation rule list page size
Two evidence-backed fixes, no operation added or removed (338 public
operations before and after).
1. Monitors, investigation_targets (hard breakage). monit-webapi reworked the
drill-down contract after this spec was last regenerated (2026-09-10), so the
documented shape is now rejected by the server: InvestigationTarget
unmarshals with DisallowUnknownFields, and time_range is mandatory.
- InvestigationTarget: kind enum gains query; time_range added and required;
query payload added (query kind).
- DashboardInvestigationTarget: variable_bindings replaced by the variables
string map that now carries the same event-label templates.
- New: InvestigationTimeRange, QueryInvestigationTarget, DashboardQuery.
- Removed: InvestigationVariableBinding (orphaned by the change).
- AlertRuleV2.investigation_targets: maxItems 20.
This was the flag raised by the earlier Monitors doc review as a
must-fix-by-api-review item; doc-following requests were being rejected.
2. AI SRE, POST /safari/automation/rule/list. AutomationRuleListRequest
.properties.limit gains maximum 200 and a description stating the real
bounds, matching the explicit cap in fc-safari logic/automation/service.go.
Diff: 4 files, +376/-68. Key order preserved everywhere (verified: the
relative order of every pre-existing key is byte-identical to HEAD; no
reordering noise). docs.json and both api-catalog.mdx untouched.
docs(api): daily audit 2026-09-16 — repair the investigation_targets drill-down contract, cap the Automation rule list page size
docs: doc-review 2026-09-15 (diff mode) — alert-rule no-data/recovery mode, data-source & Go SDK updates
docs(api): daily audit 2026-09-15 — surface template closed-card action apps, session and feed fields
…itories docs(api): document linked source code repositories on RUM applications
docs: update Aliyun DataWorks Op alert key semantics and display name
… 12 low)
Window: 2026-09-15T08:18:21Z -> 2026-09-16T08:05Z (diff mode, scope all).
Covers the AI SRE paid launch, the plugin-catalog/connect-dialog rework,
edge engine server-pushed auto-upgrade, incident-timeline 接续对话 entry,
and the on-call war-room switch / datasource ${env:} coverage fixes.
zh first, en derived; no file renames, so no redirects needed.
docs: daily doc-review 2026-09-16 (31 findings)
/member/notify returns this advisory field when the submitted HTML body does not follow the default email layout (no max-width:600px wrapper), on dry runs and real sends alike.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the new advisory
agent_instructionsfield on the/member/notifyresponse (all four spec files: openapi + platform.openapi, en + zh). Present when the submitted HTML body lacks the default email layout'smax-width:600pxwrapper; advisory only, returned on dry runs and real sends alike.