V3 Content Audit — 2026-02-27

Scope

• Scanned active docs in docs_hub_v3 excluding 06_BASELINE_ARCHIVE.
• Focus: stale references, status consistency, duplicate files, placeholder quality.

Summary

• Legacy V2 references in active docs: 31 → 20 after consistency patch.
• Remaining 20 references are all in migration records under 99_MIGRATION/ (expected).
• Broken markdown links in active docs: 150 → 1 after remediation; remaining 1 is scanner false-positive on regex text in 02_SPECS/core/tenant_onboarding/01_db_schema.md.
• Exact duplicate files in active docs: 10 → 0 after shared-template dedup (02_SPECS/modules/_shared/DELIVERY_PACK_TEMPLATE.md + module wrappers).
• Major consistency risk remains: FEATURE_STATUS_MATRIX and MODULE_INDEX represent different status semantics.

Findings & Proposed Actions

P0 — Status Model Consistency

1. Issue: 03_TRACEABILITY/FEATURE_STATUS_MATRIX.md uses execution lifecycle (IN_PROGRESS, DONE, ...), while 02_SPECS/MODULE_INDEX.md uses legacy plan completion semantics (✅/⚪/🟡).
2. Action Applied: Added explicit disclaimer in MODULE_INDEX:
   • status is Legacy Plan Status,
   • runtime execution truth is 03_TRACEABILITY/FEATURE_STATUS_MATRIX.md.
3. Action Applied: Added SoT note directly in 03_TRACEABILITY/FEATURE_STATUS_MATRIX.md to mark this file as authoritative for delivery/runtime status.
4. Action Applied:
   • Added Legacy↔Runtime mapping block in both 02_SPECS/MODULE_INDEX.md and 03_TRACEABILITY/FEATURE_STATUS_MATRIX.md.

P1 — Legacy Reference Cleanup in Active Docs

1. Issue: Several active operational docs still pointed to docs_hub_v2 paths.
2. Action Applied:
   • Updated active docs to docs_hub_v3 structure in:
     • 04_OPERATIONS/05_PROJECT_OPERATING_SYSTEM.md
     • 04_OPERATIONS/06_ENGINEERING_RULES.md
     • 04_OPERATIONS/04_ROADMAP.md
     • 02_SPECS/workitems/WI-SEC-001__permissions_guard_hardening.md
     • 03_TRACEABILITY/WORKITEM_BOARD.md
     • plus DocHub title normalization in governance/architecture files.
3. Remaining: Legacy mentions exist only in migration docs (intentional historical records).

P2 — Duplicate Content Control

1. Issue: 10 exact duplicates in module-level DELIVERY_PACK.md files.
2. Action Applied:
   • Added shared template: 02_SPECS/modules/_shared/DELIVERY_PACK_TEMPLATE.md.
   • Replaced 10 duplicated packs with module-specific wrapper/index files referencing shared template.
   • Benefit: lower drift and easier bulk updates.

P2 — Generated Placeholder Quality

1. Issue: 05_GENERATED/backend_entity_manifest.md still contains many TBD fields.
2. Action Applied:
   • Added WI-DOC-002 in 03_TRACEABILITY/WORKITEM_BOARD.md for manifest enrichment rules (collection mapping, owner module, confidence).
   • Added detailed workitem spec: 02_SPECS/workitems/WI-DOC-002__entity_manifest_enrichment.md (output schema, acceptance criteria, regenerate cadence).
   • Executed generator update in v2/scripts/generate_manifests.js and regenerated manifest at 05_GENERATED/backend_entity_manifest.md with enriched columns (Owner Module, Source Path, Confidence).
3. Execution Result (2026-02-27):
   • Collection/Table = TBD: 0 (from baseline mostly TBD)
   • Confidence distribution: HIGH=74, MEDIUM=3, LOW=24
   • Current backlog focus shifts from missing collection info to LOW-confidence review queue.
4. Action Applied:
   • Completed LOW-confidence triage in 04_OPERATIONS/12_WI-DOC-002_LOW_CONFIDENCE_TRIAGE_2026-02-27.md.
   • Result: 24/24 LOW rows are expected embedded schemas (_id:false), unresolved mapping count = 0.
5. Action Applied:
   • Added generator quality guard in v2/scripts/generate_manifests.js:
     • hard-fail nếu row thiếu Owner Module hoặc confidence ngoài HIGH|MEDIUM|LOW,
     • warning-only cho LOW rows có note khác embedded schema (_id:false).
6. Action Applied:
   • Added CI workflow .github/workflows/manifest-guard.yml để chạy v2 manifest guard tự động trên pull request.
   • Added npm scripts trong v2/package.json: generate:manifests, ci:manifest-guard.
   • Local validation passed: npm.cmd run ci:manifest-guard.
7. Action Applied:
   • Standardized GitLab enforcement with .gitlab-ci.yml job manifest_guard (MR/default-branch pipelines).
   • Added branch protection runbook 04_OPERATIONS/13_BRANCH_PROTECTION_POLICY.md to require successful pipeline before merge.
8. Action Applied:
   • Added one-command verifier v2/scripts/verify_gitlab_enforcement.js + npm script verify:gitlab-enforcement.
   • Live verification result: all checks PASS (auth, merge gates, protected branch policy, manifest_guard presence).

Suggested Next Batch

1. Optional: rotate temporary access token used during setup and keep verification command for periodic audits.