Operations: rename shard stat autoConflationEnabled to conflationRuleApplied Match the push-distribution-server REST field rename. Also distinguish it from autoConflationEngaged (rule matched vs conflation currently active) in the accompanying prose.
Real health-check examples, gateway role: n/a note, and cookbook health cross-links Operations-Monitoring's "Is the system healthy?" example swaps the mf-mds-consolidated + mf-eta-simulator placeholder for a real Static MDS response (gateway, core services, two feed-partitioned projectors, admin) and rewords the lead-in now that the gateway correctly shows role: n/a rather than ACTIVE. Quick Start's Step 5 example gets the same n/a correction plus a short note that it is normal, not a problem. Each Deployment Cookbook page (Static MDS, Fine-Grained, Static MDS with Compute, Scalable MDS, Demo) gets a "Confirm it's running" pointer to that same health-check section in its Where to go next list. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Fix a third double-bracket JSON array (multi-line) The multi-line component-state example in Operations: Monitoring was also wrapped in [[ ]] instead of a single-bracket JSON array. Correct to [ ]. Wiki-wide re-scan confirms no [[ / ]] code-array artifacts remain and every [[...]] link resolves to a real page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Fix double-bracket JSON/SQL example arrays Two example payloads in code fences were wrapped in [[ ]] (which renders literally) instead of single-bracket JSON/SQL arrays. Correct to [ ]. 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
Move Component state to Architecture: Basics Component state is a foundational lifecycle concept (referenced by Monitoring, Troubleshooting, Logging), and read orphaned at the tail of Architecture: Advanced. Move the section - definition, two-phase model, and state diagram - into Architecture: Basics after "How a request is handled". Retarget the state-model references (Troubleshooting FAQ, Operations: Monitoring, How-to-Read) to Basics; trim the Advanced intro; add a state<->role pointer between the two pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Operations: Monitoring - per-container versions by systemID predicate osgi-bootstrap now exposes systemID as a non-identity @APIResource (MetaFluent/IssueTracking#633), so use-case 1 selects a container's bundles by the same identity used for logs and state: systemID=<systemID>/bundles?bundleName=.* Also removes the earlier availability caveat (its premise was a gateway duplicate-@APIIdentity conflict, since fixed, not an IDE limitation). Verified live. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Operations: Monitoring - note osgi-bootstrap availability (bootstrap-dependent) osgi-bootstrap is only in the catalog where the deployment is bootstrapped; a bare IDE/dev launch has no bootstrap layer and no osgi-bootstrap API, so version queries are unavailable there. Observed live (present on a bootstrapped container deployment, absent on a non-bootstrapped launch). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Operations: Monitoring - add Component versions (osgi-bootstrap) Two use-cases via the osgi-bootstrap /bundles?bundleName=<regex> resource (name/version/state): what components and versions run in a container, and what version of a given component is deployed system-wide (drift check via * sweeping every container). Notes that the osgi-bootstrap instance id is its own, not the application-state systemID. Verified live. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Operations: account for standby role in health checks (redundant deployments) Monitoring: "healthy" now depends on role - ACTIVE/n-a should be FULLY_OPERATIONAL, STANDBY is healthy at RESOURCE_COMPLETE (awaiting activation). Adds a redundant-deployment example so a hot standby is not misread as broken. Troubleshooting: rebuild the cluster section as "Cluster and redundancy" - lead with the healthy-standby signature (role=STANDBY predicate call, real output), the same-named-pair/systemID note and the lone-dot-path gotcha, then symptoms (standby normal-at-RESOURCE_COMPLETE, missing component, no ACTIVE, standby-did-not-promote). Grounded in a live redundant cluster. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Operations: use camelCase system sub-objects (summary/details/stats) REST field-name standardization (MetaFluent/IssueTracking#602): the application-state `system` object's sub-objects were PascalCase (Summary/Details/Stats) and are now camelCase. Update the affected projection URLs and JSON samples in Monitoring and Logging. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Operations: Monitoring - use real ETA feed-loss failure for which-part/why (Projector RECOVERING + real history)
Add Operations: Logging (use-case-driven log queries, real ETA feed-loss examples); link from sidebar + Monitoring
Operations: Monitoring - add real sample output to Resource monitoring + Logs queries; correct shard metric (updates/sec + conflation, not per-shard bytes)
Architecture: Advanced - add public component-state lifecycle diagram (trimmed for customers); link from Operations state table
Operations: Monitoring - real OperationalState table, real history format, drop fabricated state
Scaffold Elastic MDS wiki: Home, sidebar, footer, page stubs for the full doc set