Reframe Docker-centric wording so the conventional path is a first-class option Deployment-Basics.md's "What a deployment is made of" now opens with the substrate-neutral framing (conventional / Docker / Kubernetes all run the same base image and deployment-config), and "Running a deployment" leads with that same three-way framing before presenting the deploy-mf-<service> / scripts/start workflow as one way to bring a service up under Docker, pointing to the Cookbook and Deployment: Without Docker for the other two. Sweeps the rest of the wiki for the same assumption: Architecture-Advanced mentions systemd alongside Docker/Kubernetes for automatic restart and infra-component restart, and drops "container" as the implied only unit for per-instance role reporting, topology packaging, and the operational instance count. Configuration-Basics, Configuration-Advanced, and Deployment-Advanced add the conventional option alongside Docker/Kubernetes where a mounted-config or single-network example only named Docker. Configuration-Reference notes the Docker-free way to read the annotated defaults from an installation package. Image-Catalog and Cookbook-Enable- Tokens swap a couple of "container"/"in a container" phrasings for substrate-neutral wording. Glossary's Composition entry points at the Demo cookbook page instead of a no-longer-used "consolidated composition" name. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Wiki-wide: fix cross-page and same-page section links Same mis-placed-anchor pattern as the Cookbook fix, swept across the whole wiki: 19 links across 8 pages carried the #anchor on the display side of the [[...]] pipe (or as a bare [[Section Title]]), so they landed on the page top instead of the section. Convert each to a markdown link that honors the fragment, e.g. [[Architecture: Advanced#high-availability-activestandby|active/standby]] -> [active/standby](Architecture-Advanced#high-availability-activestandby) and same-page ones to [text](#anchor). One swapped plain link ([[Configuration: Basics|setting values]]) corrected to [[setting values|Configuration-Basics]]. Every target anchor verified against a real heading. Not touched: two double-bracket JSON/SQL examples inside code fences (a separate typo, flagged for review). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Wiki sweep: mode->switch, tunable->setting for the settings layout Security: session-authn 'mode' -> authenticationDomain 'switch'. Configuration Reference: 'tunable' subset -> promoted 'settings' in the per-component settings files, vs the full configurable surface. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Configuration Reference: rename live dump section "report" not "reference" "Reference" collides with the page title and the annotated files; the gateway dump is one report within the overall reference. Rename the section heading and align the intro wording (aligns with the on-disk *ReportXMLFile.xml and the "self-report" vocabulary). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Configuration Reference: annotated per-image properties files + short/FQN naming Add the annotated-defaults mechanism as the primary "what does it mean" reference (generated per-blueprint files baked into each image under config/defaults/, comment-annotated, version-stamped; extract with docker cp / docker create). Explain short names vs fully-qualified names: the annotated files define every setting in short form, and most settings appear ONLY in short form - deployment.properties pre-lists the commonly-changed subset in FQN form, but any setting can be overridden by its FQN. Worked example uses a foundational property that IS surfaced in FQN form (the ETA feed host, manager.etaServerHost), with server.default as the short-only counter-example. Tie the two references together: self-report bundleName+name IS the FQN. All examples extracted from a real image and the live gateway. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Configuration Reference: evergreen self-report how-to Replace the placeholder with the real page: why there is no static table (settings and defaults are version- and deployment-specific and would rot), how to have the running system generate a complete, version-stamped configuration reference via config/fullProperties, how to read an entry, the tunable-vs-full-configurable-surface distinction, and diffing the dump across upgrades. All examples verified against a live consolidated deployment (field names, 6.3.0/6.8.0 version stamps, nested per-container shape, restServer.standAlone override, env-ref-to-empty, 24-bundle full dump). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Scaffold Elastic MDS wiki: Home, sidebar, footer, page stubs for the full doc set