Reposition DOGFOOD away from first-run path

[flyingrobots]

Method Card

Classification

• Issue: Reposition DOGFOOD away from first-run path #138
• Title: Reposition DOGFOOD away from first-run path
• Labels: lane:inbox, legend:df, legend:dx, priority:medium, type:docs
• Source: /Users/james/Downloads/bijou_deep_dive (1).pdf
• Source type: external deep-dive PDF critique
• Repo baseline checked during intake: 0d6b5f85

Sponsored Perspectives

• Sponsored Human: Bijou learner using DOGFOOD as the visible documentation and product proof surface.
• Sponsored Agent: DOGFOOD inspection agent that validates visible docs behavior, lowering, and smoke-test evidence.

These are Method sponsorship seats, not literal people, accounts, or model brands. The human seat names the served operator/contributor perspective; the agent seat names the automation perspective that must be able to inspect and reproduce the work.

Finding

Day 0 critique: DOGFOOD is impressive, but too complex to be the first evaluation experience.

Current Repo Note

Current-main note: this may already be partially or fully satisfied on current main; keep it as raw intake until triage verifies and closes or retitles it with a disposition.

Hill

As a new evaluator, I encounter DOGFOOD as the proof surface after a simpler success path, not as the first required mental model.

Context

This is raw Method intake from the Bijou deep-dive PDF. It must be triaged through GitHub Issues before implementation work starts.

Scope

• Verify the PDF critique against current repo truth.
• If the critique is still valid, shape the smallest coherent Method cycle or maintenance pass.
• If already satisfied, close with a disposition comment linking the proof.

Out Of Scope

• Solving adjacent PDF findings unless explicitly linked.
• Deleting or rewriting historical evidence without a separate design decision.

Acceptance Criteria

• The finding has been verified against current main.
• The issue is either moved to the correct lane with a concrete plan or closed with a documented disposition.
• Any implementation work includes tests/docs/witness appropriate to the change.

Expected Evidence

Tests

• Run DOGFOOD-focused coverage such as npm test -- --run scripts/docs-preview.test.ts scripts/smoke-dogfood.test.ts for docs-surface behavior.
• Run npm run smoke:dogfood:docs or npm run smoke:dogfood:landing when the visible DOGFOOD flow changes.
• Run npm run docs:inventory and git diff --check for documentation-only changes.

Playback

• Capture a DOGFOOD transcript or smoke output proving the documented user path, including the visible entry/exit behavior when the issue concerns terminal takeover or non-TTY handling.

Docs

• Check/update README.md.
• Check/update docs/DOGFOOD.md.

Retro / Closeout

• If implementation work happens, close with a Method retro or PR closeout that names the commands run, user-visible result, and any deferred debt.
• If the issue is closed during triage, the close comment must say one of: already satisfied, duplicate, not planned, or superseded, and include the exact evidence for that disposition.

Method Artifacts

• Design: If this issue is pulled from lane:inbox into an implementation cycle, create or link docs/design/DF-138-reposition-dogfood-away-from-first-run-path.md. If triage closes it as already satisfied, the issue close comment is the design disposition and must cite proof.
• Witness: For repo changes, include reproducible command output in the PR body or a linked witness file under docs/method/retro/DF-138-reposition-dogfood-away-from-first-run-path/. For no-code closure, include the verification commands and file references in the closing comment.
• Retro: Full cycle work closes with docs/method/retro/DF-138-reposition-dogfood-away-from-first-run-path/DF-138-reposition-dogfood-away-from-first-run-path.md. No-code or duplicate closure must include a disposition comment explaining why a retro is not required.
• PR: Required for any repo-file change and must close Reposition DOGFOOD away from first-run path #138. No PR is required only when the issue is closed as already satisfied, duplicate, or intentionally not planned with a written disposition.

Triage Rule

This issue is not done merely because a similar fix appears to exist. It is done only when the GitHub issue records the verification or links the PR/retro that proves the finding has been handled.

[coderabbitai]

🔗 Related PRs

#59 - [codex] Make DOGFOOD the canonical docs surface for 4.1.0 [merged]
#69 - feat: add story tooling and shape v6 layout lane [merged]
#76 - test(dogfood): audit data visualization stories [merged]
#78 - test(dogfood): audit app shell story [merged]
#104 - docs: align vision and bearing with DOGFOOD coverage [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[flyingrobots]

Disposition: already satisfied.

Already satisfied. DOGFOOD is no longer the first-run path: README Start Here runs install, hello, counter, then DOGFOOD, and warns that DOGFOOD is a full-screen interactive TUI (README.md:23-53).

Verification:

• npm run docs:inventory passed.
• npm test -- --run scripts/check-node-version.test.ts packages/bijou-node/src/index.test.ts scripts/smoke-canaries.test.ts scripts/docs-preview.test.ts passed; Vitest ran the existing matching focused tests: scripts/check-node-version.test.ts, packages/bijou-node/src/index.test.ts, and scripts/docs-preview.test.ts (3 files / 82 tests).
• git diff --check passed.

No repo change, PR, or Method retro is required for this closure because the issue was a verification card and the existing repo state already satisfies the finding.