Skip to content

docs: doc-claim drift detected on 2026-08-03 - #21

Open
NickCrew wants to merge 1 commit into
mainfrom
docs/drift-2026-08-03
Open

docs: doc-claim drift detected on 2026-08-03#21
NickCrew wants to merge 1 commit into
mainfrom
docs/drift-2026-08-03

Conversation

@NickCrew

@NickCrew NickCrew commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

Automated doc-drift audit of the 12-file doc set. 12 claim discrepancies found across 9 files — 10 P1 dev-doc errors and 2 P2 minor staleness items. No doc files were modified; findings are logged in the new Backlog task TASK-18.

Severity breakdown: 10 P1 (dev-doc errors affecting correctness), 2 P2 (minor staleness)

Most impactful findings:

  • AGENTS.md incorrectly states "nginx handles the proxy" in production Docker — all three Dockerfiles use uvicorn directly
  • docs/architecture.md DEMO_MODE default is true (not a valid value; actual code default is full)
  • apps/vuln-api/README.md links to docs/API-DOCUMENTATION.md which does not exist at that path
  • docs/endpoints-catalog.md internally contradicts itself: "469 unique endpoints" vs "243 Total Routes" in the same file
  • README.md and docs/developer-guide.md claim DEMO_MODE default is strict; the Python code default is full

See backlog/tasks/task-18 - Doc-drift-detected-2026-08-03.md for the full finding list with file:line citations, exact quotes, and proposed fixes.


Generated by Claude Code

12 claim discrepancies found across 9 of 12 audited doc files.
Findings logged in backlog/tasks/task-18.

NickCrew commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator Author

CI note: The Test Backend failure (test_checkout_methods_lists_available_payment_methods — 500 instead of 200) is pre-existing on the base branch. The most recent main push (07fb2e8, "docs: add Project tracking section (#14)", 2026-06-09) also concluded failure with the same CI workflow. This PR adds only a single markdown file (backlog/tasks/task-18…md) — no Python code was touched, so the checkout test failure cannot originate here.

No action from this PR is needed to fix that test; it should be addressed separately on main.


Generated by Claude Code

Sign up for free to 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