Track 3 Tier 2: MW-by-domain config, Application Links API, Mongo 7 upgrade, smart routes, L1-port filter - #20
Merged
Conversation
- Maintenance Window by Domain: document the real mechanism (a window scoped to a domain via its domain association, not a named domain setting) - New: Managing Resource Application Links (the four TestShell API methods) - MongoDB 6.0->7.0 upgrade guidance (+ Node 24 / Erlang 26 notes) - Smart Route Creation with L1 Priority: expand into a how-to - Add an L1-port filter entry to the Find Resources articles Grounded in the server code and integration tests; adversarially verified. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Fills the five PARTIAL how-to gaps from the coverage audit — features that were mentioned but not actually usable/configurable from the docs.
Changes
admin/…/maintenance-window.md) — rewritten to the real mechanism: a maintenance window is scoped by associating it with a domain (vs Global), using the same schedule/notification/message fields; Global takes precedence. Corrects the prior text, which implied a nonexistentUpdateDomainSettingkey — so the two API-guide domain-setting pages are intentionally left unchanged (no such setting exists).api-guide/shell-dev-blueprint-design-api/…, new) — the four TestShell API methods (Set/Get× resource/family-default), the disable-by-application-name value format, replace-all semantics, and resource-vs-family inheritance.install-configure/…/how-to-upgrade-4.2-6.md) — installer-vs-standalone framing, feature-compatibility-version steps, plus the 2026.1 Node 24 / Erlang 26 and x86-Node-removal notes.admin/…/assembly-lab/index.md) — expanded the note into a how-to (resolution order + numbered steps).Grounding & validation
MaintenanceWindow.DomainId+MaintenancePerDomainScenarios), and removed the pre-existing invented-key text.npm run buildpasses (only the 3 pre-existingabstract-resources.mdbroken links). AddedFCV/setFeatureCompatibilityVersion/featureCompatibilityVersion/Telnetto.wordlist.txt.🤖 Generated with Claude Code