Plan: Harness Public Entrypoints

Initial Situation

The current public Harness wiki still exposes supported work under apps/wiki/content/docs/harness/lifecycle-flows, Trust/adoption as a multi-page trust-and-adoption section, and Foundations before the work-oriented sections in apps/wiki/content/docs/harness/meta.json.

There is no current apps/wiki/content/docs/harness/entrypoints source folder. The docs app uses Fumadocs content from apps/wiki/source.config.ts, reshapes the page tree in apps/wiki/src/lib/source.ts, and serves /docs/* through apps/wiki/src/app/docs/[[...slug]]/page.tsx.

Redirects currently live in sectionLandingRedirects and adjacent redirect logic inside apps/wiki/src/app/docs/[[...slug]]/page.tsx. apps/wiki/next.config.mjs only sets headers. apps/wiki/proxy.ts handles markdown-preferred rewrites, not route migration.

The worktree already contains handoff-owned changes:

• apps/wiki/content/docs/project/grilling/meta.json
• apps/wiki/log.md
• apps/wiki/content/docs/project/grilling/harness-public-entrypoints-backlog.md

Issue

The accepted IA has moved from lifecycle-flow language to public entrypoints. Readers should understand what Harness can do from /docs/harness/entrypoints, while old lifecycle-flow links continue to work. Trust/adoption should be one page. Foundations should explain the model after entrypoints, skills, and tools have oriented readers.

Solution Shape

Use the closed grill and Linear backlog as source truth. First create docs-ingest writer artifacts for the public refactor. Then implement in dependency-aware parallel waves:

1. Writer artifacts and entrypoint overview foundation.
2. Route moves and Trust consolidation.
3. Redirects, selective links, Foundations theory, and final bookkeeping.

Resolved Decision Ledger

• Requirements are closed. No new grill needed.
• Canonical route: /docs/harness/entrypoints.
• Overview categories: Core, Atomic, Commands.
• Variants are not a top-level category.
• AFK delivery lives at /docs/harness/entrypoints/implementation/afk.
• Atomic entrypoints are parallel-research and handoff.
• Command capabilities are dp update and dp report.
• Old lifecycle-flow routes redirect to new entrypoint routes.
• Trust/adoption child content merges into one Trust page.
• Old trust/adoption child routes disappear with no redirects.
• Top-level Harness sidebar order: Entry Points, Skills, Tools, Foundations, Prompt Surface, Exec, Trust.
• /docs and /adopt header/sidebar shortcuts should be removed or replaced so they do not preserve old shortcuts from the closed grill.
• dp report mechanics link to /docs/cli/commands/report.
• dp update mechanics link to /docs/cli/scaffold-lifecycle/scaffold-update, since no /docs/cli/commands/update page exists.

Assumptions And Constraints

• dp update --check is clean as of 2026-06-27: no managed file changes and no stale files.
• The current branch is main; no branch/base stack is required by this plan.
• No reusable shared skills are edited in this plan.
• Public docs changes must use docs-ingest-phase and writer artifacts before final routed page merges.
• Existing operational substance from lifecycle pages must remain represented after retitle/move.
• Link density should improve discoverability without turning prose into a reference table.
• Trust/adoption content should be consolidated, not deleted.
• Old trust/adoption child routes should not be added to the redirect map.

Codebase Findings

• Fumadocs source root: apps/wiki/content/docs.
• Manual page tree reshape: apps/wiki/src/lib/source.ts.
• Docs route and redirect seam: apps/wiki/src/app/docs/[[...slug]]/page.tsx.
• Header links: apps/wiki/src/lib/layout.shared.tsx.
• Current lifecycle source: apps/wiki/content/docs/harness/lifecycle-flows/*.
• Current trust source: apps/wiki/content/docs/harness/trust-and-adoption/*.
• Current tools source: apps/wiki/content/docs/harness/validation-and-tools/*.
• Current Foundations pages:
  • apps/wiki/content/docs/harness/foundations/harness-operating-system.mdx
  • apps/wiki/content/docs/harness/foundations/context-engineering.mdx
  • apps/wiki/content/docs/harness/foundations/trust-model.mdx
  • apps/wiki/content/docs/harness/foundations/progressive-disclosure.mdx
• Current command targets:
  • apps/wiki/content/docs/cli/commands/report.mdx
  • apps/wiki/content/docs/cli/scaffold-lifecycle/scaffold-update.mdx

External Research

No external dependency behavior is needed for planning. The implementation uses existing Fumadocs/Next patterns already present in the repo.

Dependency Graph

T1 ─┬─ T2 ─┬─ T3 ── T4 ── T5 ── T10 ─┬─ T12 ── T13 ── T14
    │      └─ T6 ─────────────────────┘
    └─ T7 ── T8 ── T9 ── T11 ─────────┘

Parallel Execution Waves

Skill Routing

All tasks touch apps/wiki, so each task inherits root AGENTS.md plus apps/wiki/AGENTS.md.

Scoped wiki primary skills considered during planning:

• agent-browser
• async-react-patterns
• autoreview
• codebase-design
• design-taste-frontend
• frontend-domain-structure
• improve-codebase-architecture
• next-best-practices
• next-cache-components
• parallel-research
• quality-types
• react-doctor
• simplify
• tdd
• vercel-composition-patterns
• vercel-react-best-practices

Additional goal-selected orchestration skills:

• docs-ingest-phase
• writing-fragments
• writing-beats
• writing-shape
• implement-spec

Backlog Sync

Linear already contains the required epics and stories in the HARNESS-INTELLIGENCE project and M6 Public Wiki Entrypoints milestone. The local backlog mirror exists at apps/wiki/content/docs/project/grilling/harness-public-entrypoints-backlog.md.

Planning sync result: no new Linear issues are needed. Each task below references the owning product story.

Tasks

Each task touches apps/wiki and therefore inherits the full scoped wiki primary list: agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, and vercel-react-best-practices. The task-local assigned_skills field lists those plus the explicit orchestration/writing skills that shaped the task.

T1: Docs-Ingest Writer Artifact Bundle

• depends_on: []
• location: apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/**, apps/wiki/content/docs/project/public-docs/meta.json
• description: Run the public docs path of docs-ingest-phase for this public IA/content refactor. Create a writer artifact bundle with fragments.md, beats.md, shape.md, and meta.json. The bundle must cover entrypoint overview, core pages, Trust merge, tool/skill link policy, and Foundations theory shape before final routed pages are written.
• validation: Writer artifacts exist, include traceability to the grill/backlog/spec, and name target public routes before final page merges.
• status: Complete
• log:
  • 2026-06-27: Created docs-ingest public writer artifact bundle from the closed spec, plan, handoff, grill status/log, and backlog mirror. Captured fragments, beats, shape, traceability, target public routes, Trust merge guidance, tool/skill link policy, and Foundations theory shape. Did not edit routed public Harness pages.
• files edited/created:
  • apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/fragments.md
  • apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/beats.md
  • apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/shape.md
  • apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/meta.json
  • apps/wiki/content/docs/project/public-docs/meta.json
• backlog_item_id: IP-300
• backlog_item_url: https://linear.app/devpunks/issue/IP-300/reader-lands-on-a-public-entrypoint-overview
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-fragments, writing-beats, writing-shape]
• tdd_status: not_applicable
• tdd_target: Static writer artifacts prove the public docs pass has fragments, beats, and shape before final page writing.
• red_command:
• expected_red_failure:
• green_command: test -f apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/fragments.md && test -f apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/beats.md && test -f apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/shape.md && rg -n "entrypoints|Trust|Foundations|tool|skill" apps/wiki/content/docs/project/public-docs/harness-public-entrypoints
• reason_not_testable: Writer artifact creation is static documentation planning, not runtime behavior.
• red_evidence:
• green_evidence: 2026-06-27 exit 0: test -f apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/fragments.md && test -f apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/beats.md && test -f apps/wiki/content/docs/project/public-docs/harness-public-entrypoints/shape.md && rg -n "entrypoints|Trust|Foundations|tool|skill" apps/wiki/content/docs/project/public-docs/harness-public-entrypoints. Representative matches: fragments.md:38 canonical /docs/harness/entrypoints; fragments.md:136 Trust merge; fragments.md:156 Foundations after Tools; shape.md:92 tool link policy; shape.md:98 skill link policy.
• codebase_design_notes: Writer artifacts are the content seam between closed requirements and routed MDX. They keep conceptual shape out of implementation chat.
• review_mode: cli

T2: Entrypoint Overview IA Shell

• depends_on: [T1]
• location: apps/wiki/content/docs/harness/entrypoints/index.mdx, apps/wiki/content/docs/harness/entrypoints/meta.json, apps/wiki/content/docs/harness/meta.json
• description: Create the canonical /docs/harness/entrypoints overview and metadata. Group capabilities as Core, Atomic, and Commands. Do not show variants as a top-level category. Keep Get Started unchanged. Add Entry Points as the first Harness section and preserve existing target links for later tasks to fill.
• validation: /docs/harness/entrypoints is generated and the overview contains Core, Atomic, and Commands without a Variants category.
• status: Complete
• log:
• 2026-06-27: Created /docs/harness/entrypoints overview with Core, Atomic, Commands, and Where To Go Next sections. Parent integration added entrypoints to Harness metadata after review found the worker-created overview was not yet visible in the section order.
• files edited/created:
• apps/wiki/content/docs/harness/entrypoints/index.mdx
• apps/wiki/content/docs/harness/entrypoints/meta.json
• apps/wiki/content/docs/harness/meta.json
• backlog_item_id: IP-300
• backlog_item_url: https://linear.app/devpunks/issue/IP-300/reader-lands-on-a-public-entrypoint-overview
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-shape]
• tdd_status: not_applicable
• tdd_target: Fumadocs content generation and browser route smoke prove the overview route and categories.
• red_command:
• expected_red_failure:
• green_command: bun run --cwd apps/wiki check-types
• reason_not_testable: Static MDX and metadata route creation; browser smoke is the primary runtime verification.
• red_evidence:
• green_evidence: 2026-06-27: bun run --cwd apps/wiki check-types passed. rg -n '^## |Variants|dp update|dp report|parallel-research|handoff|/docs/harness/entrypoints' apps/wiki/content/docs/harness/entrypoints/index.mdx showed Core, Atomic, Commands, command links, skill source links, and entrypoint route links with no Variants match. apps/wiki/content/docs/harness/meta.json includes entrypoints after index.
• codebase_design_notes: The route folder and metadata are the public IA seam. Keep command mechanics and variant detail behind linked pages.
• review_mode: mixed

T3: Core Entrypoint Route Moves And Titles

• depends_on: [T2]
• location: apps/wiki/content/docs/harness/lifecycle-flows/requirements-to-backlog.mdx, apps/wiki/content/docs/harness/lifecycle-flows/design-phase.mdx, apps/wiki/content/docs/harness/lifecycle-flows/manual-delivery-flow.mdx, apps/wiki/content/docs/harness/lifecycle-flows/debug-with-runtime-evidence.mdx, apps/wiki/content/docs/harness/lifecycle-flows/review-current-branch.mdx, apps/wiki/content/docs/harness/lifecycle-flows/clawpatch-bug-lifecycle.mdx, apps/wiki/content/docs/harness/lifecycle-flows/maintain-wiki-after-implementation.mdx, apps/wiki/content/docs/harness/lifecycle-flows/meta.json, apps/wiki/content/docs/harness/entrypoints/brainstorming-requirements-backlog.mdx, apps/wiki/content/docs/harness/entrypoints/design.mdx, apps/wiki/content/docs/harness/entrypoints/implementation.mdx, apps/wiki/content/docs/harness/entrypoints/debugging.mdx, apps/wiki/content/docs/harness/entrypoints/review.mdx, apps/wiki/content/docs/harness/entrypoints/massive-bug-hunt-and-fix.mdx, apps/wiki/content/docs/harness/entrypoints/docs-update.mdx, apps/wiki/content/docs/harness/entrypoints/meta.json
• description: Move core lifecycle pages into the accepted entrypoint route model with locked titles and slugs. Rename requirements-to-backlog to brainstorming-requirements-backlog; manual-delivery-flow to implementation; debug-with-runtime-evidence to debugging; review-current-branch to review; clawpatch-bug-lifecycle to massive-bug-hunt-and-fix; maintain-wiki-after-implementation to docs-update; design-phase to design. Remove moved core pages from lifecycle metadata and leave AFK child routing to T4.
• validation: New core entrypoint routes exist with accepted titles and old core lifecycle source files are no longer canonical routed pages.
• status: Complete
• log:
• 2026-06-27: Moved seven core lifecycle pages into entrypoints/ with accepted intent-first titles. Removed moved core pages from lifecycle metadata while leaving AFK for T4.
• files edited/created:
• apps/wiki/content/docs/harness/entrypoints/brainstorming-requirements-backlog.mdx
• apps/wiki/content/docs/harness/entrypoints/design.mdx
• apps/wiki/content/docs/harness/entrypoints/implementation.mdx
• apps/wiki/content/docs/harness/entrypoints/debugging.mdx
• apps/wiki/content/docs/harness/entrypoints/review.mdx
• apps/wiki/content/docs/harness/entrypoints/massive-bug-hunt-and-fix.mdx
• apps/wiki/content/docs/harness/entrypoints/docs-update.mdx
• apps/wiki/content/docs/harness/entrypoints/meta.json
• apps/wiki/content/docs/harness/lifecycle-flows/meta.json
• Deleted moved core source files under apps/wiki/content/docs/harness/lifecycle-flows/.
• backlog_item_id: IP-303
• backlog_item_url: https://linear.app/devpunks/issue/IP-303/core-flow-pages-use-intent-first-titles
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-shape]
• tdd_status: not_applicable
• tdd_target: Static route move plus browser route smoke proves accepted slugs and titles.
• red_command:
• expected_red_failure:
• green_command: bun run --cwd apps/wiki check-types
• reason_not_testable: Docs route/content movement is validated through generated types and browser route checks.
• red_evidence:
• green_evidence: 2026-06-27: bun run --cwd apps/wiki check-types passed. Parent find confirmed the seven new core entrypoint files and only AFK remains under lifecycle flows. Parent rg confirmed accepted titles.
• codebase_design_notes: Route slugs are the public interface. Preserve deep page content behind the new intent-first names.
• review_mode: mixed

T4: AFK Implementation Child Route

• depends_on: [T3]
• location: apps/wiki/content/docs/harness/lifecycle-flows/afk-phase-delivery-flow.mdx, apps/wiki/content/docs/harness/entrypoints/implementation/afk.mdx, apps/wiki/content/docs/harness/entrypoints/implementation/meta.json, apps/wiki/content/docs/harness/entrypoints/meta.json
• description: Move AFK delivery under Implementation at /docs/harness/entrypoints/implementation/afk. Keep Implementation as the primary delivery entrypoint and keep AFK out of top-level overview categories.
• validation: AFK route exists under Implementation, Implementation remains primary, and AFK is not a top-level category.
• status: Complete
• log:
• 2026-06-27: Moved AFK delivery under Implementation as entrypoints/implementation/afk, removed the old lifecycle AFK page from routing, and kept AFK out of top-level Entry Points metadata.
• files edited/created:
• apps/wiki/content/docs/harness/entrypoints/implementation/afk.mdx
• apps/wiki/content/docs/harness/entrypoints/implementation/meta.json
• apps/wiki/content/docs/harness/entrypoints/meta.json
• apps/wiki/content/docs/harness/lifecycle-flows/meta.json
• Deleted apps/wiki/content/docs/harness/lifecycle-flows/afk-phase-delivery-flow.mdx.
• backlog_item_id: IP-302
• backlog_item_url: https://linear.app/devpunks/issue/IP-302/afk-delivery-is-discoverable-as-an-implementation-variant
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-shape]
• tdd_status: not_applicable
• tdd_target: Static route move plus browser route smoke proves AFK is a child of Implementation.
• red_command:
• expected_red_failure:
• green_command: bun run --cwd apps/wiki check-types
• reason_not_testable: Docs route/content movement is validated through generated types and browser route checks.
• red_evidence:
• green_evidence: 2026-06-27: bun run --cwd apps/wiki check-types passed. Parent find confirmed entrypoints/implementation/afk.mdx exists, old lifecycle AFK file is absent, implementation/meta.json lists afk, and top-level entrypoints/meta.json does not list AFK.
• codebase_design_notes: AFK is a route-level child behind the Implementation interface, not a sibling top-level entrypoint.
• review_mode: mixed

T5: Core Operational Substance Audit

• depends_on: [T4]
• location: apps/wiki/content/docs/harness/entrypoints/**/*.mdx, apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/IMPLEMENTATION-NOTES.md
• description: Audit moved core entrypoint pages against their old lifecycle sources and patch only missing operational substance. Record source-to-target evidence for requirements/backlog, design, implementation, AFK implementation, debugging, review, ClawPatch, and docs update.
• validation: Implementation notes include a preservation checklist for every moved lifecycle page, and any missing operational material is restored.
• status: Complete
• log:
• 2026-06-27: Audited all moved lifecycle pages against their source routes, patched stale AFK links, and recorded source-to-target preservation evidence in implementation notes.
• files edited/created:
• apps/wiki/content/docs/harness/entrypoints/brainstorming-requirements-backlog.mdx
• apps/wiki/content/docs/harness/entrypoints/docs-update.mdx
• apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/IMPLEMENTATION-NOTES.md
• backlog_item_id: IP-304
• backlog_item_url: https://linear.app/devpunks/issue/IP-304/core-pages-preserve-their-existing-operational-substance
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-shape]
• tdd_status: not_applicable
• tdd_target: Static source-to-target audit proves operational substance survived the move.
• red_command:
• expected_red_failure:
• green_command: rg -n "requirements|design|implementation|AFK|debug|review|ClawPatch|docs-ingest" apps/wiki/content/docs/harness/entrypoints apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/IMPLEMENTATION-NOTES.md
• reason_not_testable: Content preservation audit has no runtime behavior.
• red_evidence:
• green_evidence: 2026-06-27: rg -n "requirements|design|implementation|AFK|debug|review|ClawPatch|docs-ingest" apps/wiki/content/docs/harness/entrypoints apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/IMPLEMENTATION-NOTES.md found preservation coverage. rg -n "/docs/harness/lifecycle-flows" apps/wiki/content/docs/harness/entrypoints || true produced no matches. bun run --cwd apps/wiki check-types passed.
• codebase_design_notes: Preserve page depth behind the new public slugs; titles change the interface, not the content contract.
• review_mode: cli

T6: Command Capabilities On Overview

• depends_on: [T2]
• location: apps/wiki/content/docs/harness/entrypoints/index.mdx
• description: Add dp update and dp report as Command capabilities in the entrypoint overview. Link dp update to /docs/cli/scaffold-lifecycle/scaffold-update and dp report to /docs/cli/commands/report. Do not duplicate command mechanics.
• validation: Overview contains both commands and links to existing CLI mechanic pages.
• status: Complete
• log:
• 2026-06-27: No-op verification; T2 already added the required Command capabilities and links.
• files edited/created:
• None.
• backlog_item_id: IP-305
• backlog_item_url: https://linear.app/devpunks/issue/IP-305/entrypoint-overview-includes-command-capabilities
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-shape]
• tdd_status: not_applicable
• tdd_target: Static link scan proves command capabilities are present without new CLI docs.
• red_command:
• expected_red_failure:
• green_command: rg -n "dp update|dp report|/docs/cli/scaffold-lifecycle/scaffold-update|/docs/cli/commands/report" apps/wiki/content/docs/harness/entrypoints/index.mdx
• reason_not_testable: Content-only link addition.
• red_evidence:
• green_evidence: 2026-06-27: rg -n "dp update|dp report|/docs/cli/scaffold-lifecycle/scaffold-update|/docs/cli/commands/report" apps/wiki/content/docs/harness/entrypoints/index.mdx found all required command labels and links.
• codebase_design_notes: Overview links are adapters to existing CLI docs; command mechanics stay in CLI pages.
• review_mode: cli

T7: Trust And Adoption Merge

• depends_on: [T1]
• location: apps/wiki/content/docs/harness/trust-and-adoption/**, apps/wiki/content/docs/harness/trust.mdx
• description: Merge all useful trust/adoption child-page content into one coherent Trust page. Preserve trust boundaries, validation story, failure model, criteria checklist, golden walkthrough, support feedback loop, project usage, and report triage content.
• validation: The single Trust page contains preserved sections for every accepted source child page.
• status: Complete
• log:
• 2026-06-27: Created merged Trust page preserving the accepted trust/adoption child-page content categories. Left old child routes in place for T8 removal.
• files edited/created:
• apps/wiki/content/docs/harness/trust.mdx
• backlog_item_id: IP-306
• backlog_item_url: https://linear.app/devpunks/issue/IP-306/trust-and-adoption-content-is-merged-into-one-page
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-fragments, writing-beats, writing-shape]
• tdd_status: not_applicable
• tdd_target: Static content audit proves all source trust/adoption sections survive in the merged page.
• red_command:
• expected_red_failure:
• green_command: rg -n "Trust Boundaries|Validation Story|Failure Model|Criteria Checklist|Golden Repo Walkthrough|Support Feedback Loop|Project Usage|Backoffice Report Triage" apps/wiki/content/docs/harness/trust.mdx
• reason_not_testable: Content consolidation is validated by source-to-target audit and browser route smoke.
• red_evidence:
• green_evidence: 2026-06-27: rg -n "Trust Boundaries|Validation Story|Failure Model|Criteria Checklist|Golden Repo Walkthrough|Support Feedback Loop|Project Usage|Backoffice Report Triage" apps/wiki/content/docs/harness/trust.mdx found all required sections. bun run --cwd apps/wiki check-types passed. Style scan found no em dash and no not X, it is Y pattern in the new overview and Trust page.
• codebase_design_notes: The Trust page is now the public trust interface; child pages become implementation detail to consolidate away.
• review_mode: mixed

T8: Trust Child Route Removal

• depends_on: [T7]
• location: apps/wiki/content/docs/harness/trust-and-adoption/**, apps/wiki/src/app/docs/[[...slug]]/page.tsx
• description: Remove old trust/adoption child routes from the public IA without adding redirects. During this task, keep only the old trust/adoption index plus metadata if needed for type generation; the top-level sidebar swap to the merged Trust page belongs to T9.
• validation: Old trust/adoption child files are no longer routed, and no trust/adoption compatibility redirect exists.
• status: Complete
• log:
• 2026-06-27: Deleted old trust/adoption child pages and reduced old trust/adoption metadata to the section index only. No trust/adoption compatibility redirects were added.
• files edited/created:
• apps/wiki/content/docs/harness/trust-and-adoption/index.mdx
• apps/wiki/content/docs/harness/trust-and-adoption/meta.json
• Deleted old trust/adoption child page files.
• backlog_item_id: IP-307
• backlog_item_url: https://linear.app/devpunks/issue/IP-307/old-trustadoption-child-routes-disappear
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase]
• tdd_status: not_applicable
• tdd_target: Route smoke proves old trust/adoption child routes disappear and no redirect masks deletion.
• red_command:
• expected_red_failure:
• green_command: bun run --cwd apps/wiki check-types
• reason_not_testable: Static route removal is validated through generated types plus browser 404/no-redirect smoke.
• red_evidence:
• green_evidence: 2026-06-27: find apps/wiki/content/docs/harness/trust-and-adoption -maxdepth 1 -type f | sort showed only index.mdx and meta.json. bun run --cwd apps/wiki check-types passed. Parent scan found remaining stale child-route mentions only in out-of-scope source provenance/home links for later integration cleanup.
• codebase_design_notes: Avoid compatibility adapters for trust/adoption children by design; the new public seam is the single Trust page.
• review_mode: mixed

T9: Trust Sidebar Visibility

• depends_on: [T8]
• location: apps/wiki/content/docs/harness/meta.json
• description: Keep Trust visible in the Harness sidebar after Exec, without moving it above Entry Points, Skills, Tools, Foundations, Prompt Surface, or Exec.
• validation: Harness metadata includes trust after execution-modes.
• status: Complete
• log:
• 2026-06-27: Replaced the old top-level trust-and-adoption sidebar entry with trust, keeping Trust visible after execution/tool sections for now. Final order remains T11.
• files edited/created:
• apps/wiki/content/docs/harness/meta.json
• backlog_item_id: IP-308
• backlog_item_url: https://linear.app/devpunks/issue/IP-308/trust-remains-visible-in-the-top-level-harness-sidebar
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase]
• tdd_status: not_applicable
• tdd_target: Static metadata audit proves Trust remains visible after Exec.
• red_command:
• expected_red_failure:
• green_command: rg -n '"execution-modes".*"trust"|"trust"' apps/wiki/content/docs/harness/meta.json
• reason_not_testable: Sidebar metadata update.
• red_evidence:
• green_evidence: 2026-06-27: cat apps/wiki/content/docs/harness/meta.json showed trust present and trust-and-adoption absent. bun run --cwd apps/wiki check-types passed.
• codebase_design_notes: Sidebar order is the navigation interface; Trust remains findable without competing with first-action surfaces.
• review_mode: cli

T10: Lifecycle Redirects And Header Shortcut Cleanup

• depends_on: [T5]
• location: apps/wiki/src/app/docs/[[...slug]]/page.tsx, apps/wiki/src/lib/layout.shared.tsx, apps/wiki/src/app/(home)/page.tsx
• description: Add redirects from every old lifecycle-flow URL to the accepted new entrypoint route. Remove or replace stale /docs and /adopt header shortcuts from the public navigation surface. Do not redirect old trust/adoption child routes.
• validation: Redirect map covers the locked lifecycle routes, header shortcuts no longer preserve old /docs or /adopt behavior, and trust/adoption child routes are absent from redirect logic.
• status: Complete
• log:
• 2026-06-27: Added lifecycle-flow compatibility redirects, replaced header shortcuts with Entry Points and Trust, updated home-page links, and resolved missing title frontmatter that blocked production redirect smoke.
• files edited/created:
• apps/wiki/src/app/docs/[[...slug]]/page.tsx
• apps/wiki/src/lib/layout.shared.tsx
• apps/wiki/src/app/(home)/page.tsx
• apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/SPEC.md
• apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/PLAN.md
• apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/IMPLEMENTATION-NOTES.md
• apps/wiki/content/docs/project/specs/cli/IP-273-design-phase-asset-evidence/SPEC.md
• apps/wiki/content/docs/project/specs/cli/IP-273-design-phase-asset-evidence/PLAN.md
• apps/wiki/content/docs/project/specs/cli/IP-273-design-phase-asset-evidence/IMPLEMENTATION-NOTES.md
• backlog_item_id: IP-301
• backlog_item_url: https://linear.app/devpunks/issue/IP-301/existing-lifecycle-flow-links-continue-to-work
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase]
• tdd_status: required
• tdd_target: Old lifecycle-flow public URLs redirect to accepted /docs/harness/entrypoints routes, while trust/adoption child URLs do not redirect.
• red_command: bun run --cwd apps/wiki build && sh -c 'bun run --cwd apps/wiki start > /tmp/harness-wiki-redirect-red.log 2>&1 & pid=$!; trap "kill $pid 2>/dev/null || true" EXIT; sleep 3; curl -I -s http://localhost:3000/docs/harness/lifecycle-flows | rg "location: /docs/harness/entrypoints"'
• expected_red_failure: Before implementation, the lifecycle-flow landing redirects to /docs/harness/lifecycle-flows/requirements-to-backlog or old pages instead of /docs/harness/entrypoints, so the location assertion fails.
• green_command: bun run --cwd apps/wiki build && sh -c 'bun run --cwd apps/wiki start > /tmp/harness-wiki-redirect-green.log 2>&1 & pid=$!; trap "kill $pid 2>/dev/null || true" EXIT; sleep 3; curl -I -s http://localhost:3000/docs/harness/lifecycle-flows | rg "location: /docs/harness/entrypoints" && curl -I -s http://localhost:3000/docs/harness/lifecycle-flows/afk-phase-delivery-flow | rg "location: /docs/harness/entrypoints/implementation/afk" && ! curl -I -s http://localhost:3000/docs/harness/trust-and-adoption/trust-boundaries | rg -i "location:"'
• reason_not_testable:
• red_evidence: 2026-06-27: Before implementation, equivalent RED assertion failed as expected: lifecycle-flow landing did not redirect to /docs/harness/entrypoints. The original build-backed RED command was initially blocked by missing title frontmatter in routed project spec docs.
• green_evidence: 2026-06-27: bun run --cwd apps/wiki build passed after adding required title frontmatter to routed spec docs. Runtime smoke on PORT=3050 passed: /docs/harness/lifecycle-flows redirected to /docs/harness/entrypoints, /docs/harness/lifecycle-flows/afk-phase-delivery-flow redirected to /docs/harness/entrypoints/implementation/afk, and /docs/harness/trust-and-adoption/trust-boundaries produced no location redirect. bun run --cwd apps/wiki check-types and git diff --check passed.
• codebase_design_notes: redirectSectionLanding is the route-migration adapter. Keep migration aliases centralized rather than scattering redirect components through content pages.
• review_mode: mixed

T11: Foundations Theory And Final Sidebar Order

• depends_on: [T9]
• location: apps/wiki/content/docs/harness/foundations/*.mdx, apps/wiki/content/docs/harness/meta.json
• description: Move Foundations after Tools in the top-level Harness sidebar and strengthen theory signal across all four Foundations pages. Make Foundations explain why the model works rather than first-action operator steps.
• validation: Harness metadata order matches Entry Points, Skills, Tools, Foundations, Prompt Surface, Exec, Trust, and each Foundations page gains explicit theory framing.
• status: Complete
• log:
• 2026-06-27: Reordered Harness metadata to Entry Points, Skills, Tools, Foundations, Prompt Surface, Exec, Trust and strengthened theory framing across all four Foundations pages.
• files edited/created:
• apps/wiki/content/docs/harness/meta.json
• apps/wiki/content/docs/harness/foundations/harness-operating-system.mdx
• apps/wiki/content/docs/harness/foundations/context-engineering.mdx
• apps/wiki/content/docs/harness/foundations/progressive-disclosure.mdx
• apps/wiki/content/docs/harness/foundations/trust-model.mdx
• backlog_item_id: IP-311
• backlog_item_url: https://linear.app/devpunks/issue/IP-311/foundations-moves-after-tools-with-stronger-theory
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-fragments, writing-beats, writing-shape]
• tdd_status: not_applicable
• tdd_target: Static metadata and content audit proves order plus theory additions.
• red_command:
• expected_red_failure:
• green_command: rg -n "theory|model|why|because|tradeoff|operating system|context|trust|progressive disclosure" apps/wiki/content/docs/harness/foundations
• reason_not_testable: Public docs prose and metadata update.
• red_evidence:
• green_evidence: 2026-06-27: cat apps/wiki/content/docs/harness/meta.json showed final order index, entrypoints, skills-and-packs, validation-and-tools, foundations, prompt-surfaces, execution-modes, trust. Theory keyword scan matched all four Foundations pages; style scan found no em dash or not .* it is; bun run --cwd apps/wiki check-types passed.
• codebase_design_notes: Foundations is a conceptual layer behind entrypoint and tool interfaces, not another command adapter.
• review_mode: cli

T12: Tool Mention Link Pass

• depends_on: [T10, T11]
• location: apps/wiki/content/docs/harness/**/*.mdx
• description: Selectively link meaningful tool mentions to existing validation/tool pages. Use Validation Gates, External Tool Contract, and Hooks as canonical targets where appropriate. Avoid turning prose into a reference table.
• validation: Meaningful tool mentions link to relevant routed pages and prose remains readable.
• status: Complete
• log:
• 2026-06-27: Added selective validation/tool, hook, scaffold update, and report command links. Updated remaining old lifecycle links in public Harness MDX to new entrypoint routes.
• files edited/created:
• apps/wiki/content/docs/harness/validation-and-tools/validation-gates.mdx
• apps/wiki/content/docs/harness/validation-and-tools/external-tool-contract.mdx
• apps/wiki/content/docs/harness/index.mdx
• apps/wiki/content/docs/harness/execution-modes/manual-hitl-flow.mdx
• apps/wiki/content/docs/harness/execution-modes/goal-mode-and-afk.mdx
• apps/wiki/content/docs/harness/skills-and-packs/phase-wrappers.mdx
• apps/wiki/content/docs/harness/trust.mdx
• apps/wiki/content/docs/harness/prompt-surfaces/prompt-surfaces.mdx
• backlog_item_id: IP-309
• backlog_item_url: https://linear.app/devpunks/issue/IP-309/tool-mentions-point-readers-to-validationtool-pages
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-shape]
• tdd_status: not_applicable
• tdd_target: Static link audit proves tool discoverability links are present without over-linking.
• red_command:
• expected_red_failure:
• green_command: rg -n "/docs/harness/validation-and-tools/(validation-gates|external-tool-contract|hooks)" apps/wiki/content/docs/harness
• reason_not_testable: Content link pass.
• red_evidence:
• green_evidence: 2026-06-27: rg -n "/docs/harness/validation-and-tools/(validation-gates|external-tool-contract|hooks)|/docs/cli/(scaffold-lifecycle/scaffold-update|commands/report)" apps/wiki/content/docs/harness found canonical tool/command links. rg -n "/docs/harness/lifecycle-flows" apps/wiki/content/docs/harness || true produced no matches. bun run --cwd apps/wiki check-types and git diff --check -- apps/wiki/content/docs/harness passed.
• codebase_design_notes: Links are lightweight adapters to tool docs; do not duplicate tool docs inside narrative pages.
• review_mode: cli

T13: Skill Mention Source Link Pass

• depends_on: [T12]
• location: apps/wiki/content/docs/harness/**/*.mdx
• description: Link skill mentions to accepted GitHub source URLs. Required links include parallel-research and handoff; other skill mentions should use the accepted source pattern when the source path is known.
• validation: Required skill source links exist and the wiki does not duplicate skill source docs.
• status: Complete
• log:
• 2026-06-27: Linked high-intent parallel-research and handoff mentions to accepted source URLs in conceptual skill pages and clarified the Skill Reference source-link role.
• files edited/created:
• apps/wiki/content/docs/harness/skills-and-packs/atomic-skills.mdx
• apps/wiki/content/docs/harness/skills-and-packs/skill-model.mdx
• apps/wiki/content/docs/harness/skills-and-packs/skill-reference.mdx
• backlog_item_id: IP-310
• backlog_item_url: https://linear.app/devpunks/issue/IP-310/skill-mentions-point-readers-to-source
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, docs-ingest-phase, writing-shape]
• tdd_status: not_applicable
• tdd_target: Static link audit proves required skill source links exist.
• red_command:
• expected_red_failure:
• green_command: rg -n "github.com/wearedevpunks/skills/tree/main/skills/agnostic/research/parallel-research|github.com/wearedevpunks/skills/tree/main/skills/agnostic/generic/handoff" apps/wiki/content/docs/harness
• reason_not_testable: Content link pass.
• red_evidence:
• green_evidence: 2026-06-27: rg -n "github.com/wearedevpunks/skills/(tree|blob)/main/skills/agnostic/(research/parallel-research|generic/handoff)" apps/wiki/content/docs/harness found source links in atomic skills, skill model, entrypoint overview, and Skill Reference catalog rows. bun run --cwd apps/wiki check-types and git diff --check -- apps/wiki/content/docs/harness passed.
• codebase_design_notes: Skill links are source adapters; do not mirror source skill docs into public wiki prose.
• review_mode: cli

T14: Final Docs Bookkeeping, Validation, And Acceptance Audit

• depends_on: [T13]
• location: apps/wiki/log.md, apps/wiki/index.md, apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/PLAN.md, apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/IMPLEMENTATION-NOTES.md, Linear IP-296..IP-311
• description: Finish implementation notes, task evidence, docs-ingest outcome, wiki log/index bookkeeping, Linear/backlog evidence, and manual review checklist. Run narrow-to-wide validation and browser smoke.
• validation: Wiki checks pass or blockers are recorded; manual audit maps every IP-296..IP-311 acceptance signal to evidence.
• status: Complete
• log:
• 2026-06-27: Updated final docs bookkeeping, recorded IP-296 through IP-311 acceptance checklist, ran final validation, and confirmed runtime route compatibility.
• files edited/created:
• apps/wiki/log.md
• apps/wiki/index.md
• docs/README.md
• apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/PLAN.md
• apps/wiki/content/docs/project/specs/wiki/harness-public-entrypoints/IMPLEMENTATION-NOTES.md
• backlog_item_id: IP-296
• backlog_item_url: https://linear.app/devpunks/issue/IP-296/public-wiki-entrypoint-ia-and-route-compatibility
• relation_mode: native
• assigned_skills: [agent-browser, async-react-patterns, autoreview, codebase-design, design-taste-frontend, frontend-domain-structure, improve-codebase-architecture, next-best-practices, next-cache-components, parallel-research, quality-types, react-doctor, simplify, tdd, vercel-composition-patterns, vercel-react-best-practices, implement-spec, docs-ingest-phase]
• tdd_status: not_applicable
• tdd_target: Final validation and acceptance audit prove the implemented docs surface against all stories.
• red_command:
• expected_red_failure:
• green_command: bun run --cwd apps/wiki check-types && bun run --cwd apps/wiki check && bun run --cwd apps/wiki build
• reason_not_testable: Final validation aggregates docs/content/browser evidence instead of changing behavior itself.
• red_evidence:
• green_evidence: 2026-06-27: bun run --cwd apps/wiki check, bun run --cwd apps/wiki check-types, and bun run --cwd apps/wiki build passed. Runtime redirect smoke on PORT=3050 confirmed old lifecycle landing, requirements/backlog, and AFK routes redirect to new entrypoints, while old trust/adoption child route has no redirect. Targeted scans confirmed public Harness MDX has no old lifecycle links and contains required tool/skill links.
• codebase_design_notes: Implementation notes and plan are the durable execution interface for future maintainers and reviewers.
• review_mode: mixed

Testing Strategy

• Run dp update --check before relying on scaffolded agents or skill surfaces.
• Run bun run --cwd apps/wiki check-types after route/content movement.
• Run bun run --cwd apps/wiki check before final acceptance.
• Run bun run --cwd apps/wiki build if feasible.
• Run browser smoke for:
  • /docs/harness/entrypoints
  • each new entrypoint child route
  • /docs/harness/entrypoints/implementation/afk
  • old lifecycle-flow redirects
  • old trust/adoption child routes not redirecting
  • sidebar order
• Run content audit for:
  • Core operational substance preserved
  • Trust/adoption content preserved
  • Tool and skill links resolve
  • Foundations theory signal strengthened without becoming operator quickstart prose

Risks And Mitigations

• Risk: Large route move breaks many links. Mitigation: Centralize lifecycle redirects, scan old links, and browser-smoke the route matrix.
• Risk: Trust consolidation deletes useful content. Mitigation: Require source-to-target content audit against every trust/adoption child page.
• Risk: Parallel workers collide on harness/meta.json or overview content. Mitigation: Use waves and narrow write scopes; only T2, T6, and T9 touch final Harness metadata in dependency order.
• Risk: dp update scaffold drift invalidates local skills. Mitigation: Already checked clean on 2026-06-27; rerun if scaffolding surfaces are modified.
• Risk: Link pass over-links prose. Mitigation: Select only meaningful tool/skill mentions; do not convert narrative pages to reference tables.

Unresolved Questions

None blocking. dp update is clean, Linear issue truth matches the backlog mirror, and the closed grill resolves the IA decisions.

Create-Plan Review Notes

• $grilling: ambiguity reduction found no open plan-shaping questions because the grill status is 100% closed.
• $parallel-research: used one readonly planning-discovery subagent plus local parallel inspections.
• $swarm-planner: graph uses explicit dependencies and parallel waves with disjoint primary write scopes.
• $tdd: tasks are classified as required only where route behavior needs public redirect proof; docs-only tasks use not_applicable with reason.
• $codebase-design: route migration seam is redirectSectionLanding; public docs IA is the metadata/content seam; writer artifacts are the conceptual content seam.