alignment_status: review

Documentation Drift Inventory

Devtool docs audit review page. Date: 2026-06-14. Canonical markdown artifact: research/devtool-docs-audit.md.

This page renders the full decision-relevant audit content for reviewing documentation drift across root docs, docs/, active skill contracts, pack metadata, package docs, tasks, prompts, research, specs, and alignment pages.

Table of Contents

Executive Verdict

P0: none found. The main skillpacks package metadata, primary install-route contract, and generated active pack manifest do not appear structurally broken.

P1: active devtool-docs-audit references a missing ## Next-Skill Routing section.

P1: current business-pack docs mix canonical business-research with compatibility alias business-discovery, and some compatibility descriptions omit customer-lifecycle.

P1: docs/skill-next-step-contracts.md still routes Pattern A positioning framework work through tasks/todo.md and /exec, conflicting with the Research Session Loop.

P2: the Canonical Agentic Workflow Report still uses pre-prototype specs/ paths where current product-design contracts use design/.

P2: docs/skillpacks-npm-distribution.md is internally inconsistent about whether skillpacks or gskp is the primary npm package.

P3: archive/task/benchmark/prompt drift is expected historical drift unless current docs present those artifacts as live guidance.

Inventory

The repository has 4,779 repo-owned Markdown/HTML/RST/ADOC files after excluding dependency docs, app build output, and package build output.

1,019Active pack docs and active pack skill/pack surfaces
1,771Archived pack docs
227Installed Codex skill docs
80Docs under docs/
121Task docs
170Benchmark reports
32Specs
16Research docs
51Alignment pages
394Prompt logs
Documentation classCountNotes
Active pack docs and active pack SKILL.md/PACK.md surfaces1,019Active skill contracts, alignment bundles, and pack metadata under packs/ excluding archives.
Archived pack skill/docs surfaces1,771Versioned historical snapshots under packs/**/archive/**.
Installed Codex skill copies227Current local install surface under .codex/skills.
Public/reference docs under docs/80Canonical conventions, quickstarts, package docs, generated showcase assets, historical docs.
Task docs under tasks/121Current plans plus historical ship manifests and review notes.
Benchmark reports under benchmark/170Historical test and triage outputs.
Specs under specs/32Product/spec artifacts, some historical design-phase documents.
Research docs under research/16Active research outputs and working packets.
Alignment pages under alignment/51Current and historical review/approval pages, plus index.
Prompt logs under prompts/394Invocation history, intentionally historical.

Findings

P1 - devtool-docs-audit References Missing Next-Skill Routing Rules

Active Codex, Claude, and installed copies reference a local ## Next-Skill Routing section that is absent. Evidence: packs/devtool/codex/devtool-docs-audit/SKILL.md:17 points to the section, while lines 19-25 contain only alignment-page and shipping-contract sections.

Recommended cleanup: add the routing section to both mirrors, or remove the local-section reference and use the shared shipping contract.

P1 - Business Pack Naming Drift

Active pack directories and generated manifest use business-research; docs and pack metadata still often present business-discovery as the active name. The CLI intentionally accepts business-discovery as an alias, so this is terminology drift rather than a hard install break.

Evidence includes packages/skillpacks/src/cli/pack-normalization.mjs:13-14, README.md:90, docs/packs.md:120, and docs/packs.md:137. The last also omits customer-lifecycle from the business-app compatibility expansion.

Recommended cleanup: use business-research as primary wording and mention business-discovery only as a compatibility alias.

P1 - Pattern A Positioning Still Routes Through /exec

docs/research-session-loop-convention.md says Pattern A research orchestrators use self re-invocation and run manifests rather than tasks/todo.md plus /exec. docs/skill-next-step-contracts.md:84 and line 86 still tell positioning framework selection to write work to tasks/todo.md.

Recommended cleanup: update those rows to the Research Session Loop contract and add a focused scan preventing this regression.

P2 - Canonical Workflow Report Uses Old specs/ Paths

docs/canonical-workflow-report.md:16-18 says pre-prototype UX/UI artifacts live in specs/, while docs/prototype-session-loop-convention.md:86-90 says pre-prototype design artifacts live in design/ and specs/ is for finalized post-prototype implementation specs.

Recommended cleanup: update the report or mark it as a historical snapshot.

P2 - npm Distribution Doc Has Old gskp-Primary Text

The top of docs/skillpacks-npm-distribution.md says skillpacks is primary and @glexcorp/gskp is scoped alias. Later sections still say gskp is the only npm package and bin name and ask maintainers to confirm gskp publish rights.

Recommended cleanup: split current decisions from historical planning notes and update old manifest snippets to use business-research.

P3 - Historical Surfaces Need Currentness Labels

Most drift in archives, prompt logs, task history, and benchmark reports is expected. The risk is discoverability: current indexes or root docs can make old pages look like live guidance.

Recommended cleanup: add Status: active contract, Status: historical snapshot, Status: generated, or Status: task history to high-visibility docs.

Evidence Matrix

ClaimEvidenceInferenceConfidenceDecision impact
Missing devtool-docs-audit routing sectionActive skill references ## Next-Skill Routing; file has no such sectionActive contract points to absent rulesHighPatch skill mirrors or remove reference
Business pack naming inconsistentManifest and dirs use business-research; docs use business-discovery; alias existsCommands may work, but docs mix canonical and alias identitiesHighStandardize docs on canonical name
Business app alias docs omit lifecycle laneCLI expands to four packs; docs/packs.md lists threeWorkflow docs can under-install AFPS lanesHighFix compatibility alias docs
Pattern A route conflictResearch loop forbids /exec; next-step table routes positioning to /execDocs disagree on execution driverHighUpdate next-step contracts
Pre-prototype artifact path driftCanonical report says specs/; prototype convention says design/Current-looking report is staleHighUpdate or label historical
npm package identity driftTop says skillpacks; later says gskp only package/binObsolete implementation plan remains in current docHighSplit current vs historical sections

Current / Needs Update / Historical Matrix

SurfaceClassificationAction
README.mdMostly currentReplace primary business-discovery examples with business-research.
docs/QUICKSTART.mdNeeds updateReplace business-discovery primary install guidance.
docs/packs.mdNeeds updateRename canonical business lane and fix business-app expansion.
docs/skill-next-step-contracts.mdNeeds updateReplace Pattern A /exec routing with Research Session Loop routing.
docs/canonical-workflow-report.mdHistorical or needs updateUpdate pre-prototype paths to design/ or label historical.
docs/skillpacks-npm-distribution.mdNeeds updateSeparate current decisions from old gskp-only planning text.
packs/devtool/{codex,claude}/devtool-docs-audit/SKILL.mdNeeds updateAdd or remove missing Next-Skill Routing reference.
packs/**/archive/**HistoricalDo not rewrite for drift.

Source Coverage Gaps

Verification

CheckResult
Repo-owned docs inventory excluding dependencies/build output4,779 files classified by path class.
Active/archived/installed skill inventory354 active pack skills, 2,172 archived skill snapshots, 53 installed Codex skills.
Targeted rg scansFound drift across pack naming, Pattern A routing, pre-prototype artifact paths, and npm package identity.
Exact line evidence checksCaptured with nl -ba for major findings.

Review Gates

Evidence Coverage

Is the evidence sufficient to prioritize documentation cleanup from this audit?

Proposed File Changes

Which cleanup path should follow this audit?

Compile Responses

Answer one or both review gates, then compile YAML for a follow-up remediation pass.