Skip to content

docs: fix everything the drift audit caught - #448

Merged
IanFrelinger merged 1 commit into
masterfrom
claude/doc-drift
Sep 1, 2026
Merged

docs: fix everything the drift audit caught#448
IanFrelinger merged 1 commit into
masterfrom
claude/doc-drift

Conversation

@IanFrelinger

Copy link
Copy Markdown
Owner

Pre-release doc-vs-source audit: 7 areas, 420 evidence lookups, ~45 verified findings fixed. Full manifest in the commit message. Highlights: two broken onboarding commands (cd Ashlar after cloning Nexo.git; pkg share <id> vs required --id), wrong GHCR image names in 7 docs, wrong API-key header in sdk.md, SECURITY.md denying v0.1.0 exists, SELF-EXTEND-AUDIT rewritten to the origin-keyed invariant the code actually enforces, api/index regenerated with its ~12 missing routes, and the CI inventory recounted against the tree (56 workflows; uat-gate — unfiltered on every PR — was documented nowhere).

Two audit claims were refuted by source inspection before fixing (the runtime-studio anchor is alive via an explicit <a id> tag) and left untouched.

Validation: uat tier8 4/4 locally; Ashlar.Client builds; only code delta is one XML doc comment.

[skip-prod-style] docs-only plus one XML comment; no production wiring changed.
[coordinated-integration]

🤖 Generated with Claude Code

A 7-area doc-vs-source audit (420 evidence lookups) before the first
nuget.org release. ~45 verified findings fixed; the notable ones:
BROKEN follow-alongs: TesterQuickstart/GettingStarted cloned Nexo.git then
`cd Ashlar` (fails); README showed `pkg share <id>` where the CLI requires
`pkg share --id <id>`; samples/README's cp command pointed at the removed
tag-scan objective; the Swagger promise 404s outside Development (now says
how to enable it).
WRONG facts: GHCR images are nexo-cli/nexo-api, not ashlar-cli/ashlar-api
(7 docs); the client header is X-Ashlar-Api-Key, not X-Api-Key (sdk.md + a
stale code comment); SECURITY.md claimed no tagged release exists (v0.1.0
does); DistributionModels' publication status ignored the artifact-only
v0.1.0 run; PUBLISHING understated the CI-packed set (Client/Sdk/Authoring
are unconditional); SELF-EXTEND-AUDIT invariant B rewritten to the
origin-keyed semantics the validator actually has (Authored roots skip;
machine-origin REQUIRES ParentId); SelfHostedAgentServer pulled the wrong
model (shipped agent set uses qwen2.5:7b); /ready exists (versioning.md
denied it); api/index gained the ~12 live routes it was missing;
kernel-coverage runs -f net10.0 not net9.0; GET /api/knowledge/query IS
wrapped (QueryKnowledgeAsync).
POST-SLIM residue: LICENSING's ValidationUtilities row, ProjectTiers'
ForgeMapHostSample row + PrimeTime-spans-commercial claim (LICENSING echoed
it), README's project counts (62 not 78; 3 commercial not 9) and layout-tree
comments, CommercialExtractionPlan status, FleetGovernanceInventory's
discover/advertise verbs (the command is `lan`) and resolved test rows,
OpenCoreBoundary's boundary summary (85 scanned, 8 commercial), the dead
APPLICATION_GATE_GAMEDOMAIN flag, CiGateInventory/workflows-README counts
(56 files, five schedules, 17 dispatch-only; uat-gate and portability-gate
added — uat-gate runs unfiltered on every PR and was documented nowhere),
mesh-lab-gate marked dormant, MiddlewareIngress catalog list, DEPLOYMENT's
nexo-api service name (compose service is ashlar-api), and the enumeration
sentence #446's line-delete mangled in the autonomy-objectives README.
Two audit claims were REFUTED before fixing: the runtime-studio anchor
"#how-runtime-studio-fits-with-ashlar-api" is alive (explicit <a id> at
README line 11 — two auditors missed it), so those links stand.
Validation: uat tier8 4/4 PASS locally; Ashlar.Client builds; the only code
change is one XML doc comment.
[skip-prod-style] docs-only plus one XML comment; no production wiring
changed.
[coordinated-integration]
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@IanFrelinger
IanFrelinger merged commit dd6b4ab into masterSep 1, 2026
16 checks passed
@IanFrelinger
IanFrelinger deleted the claude/doc-drift branch September 1, 2026 01:12
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@IanFrelinger