[MVP] Doc-driven development + evidence-driven acceptance — process workstream

[lalalune]

This is the coordination thread for the process workstream of the LifeOps
Personal Assistant MVP. If you are working on how we plan, track, document, or
prove work in this repo, coordinate here.

What we adopted

• The MVP is the LifeOps Personal Assistant: chat, onboarding, the current
  views, and centrally LifeOps — all scheduling, calendar, coordination,
  reminders, goals, todos, tasks. It serves children, adults with
  ADHD/ADD/Asperger's/autism, neurotypical people, and elderly people — no
  therapy language, no special rails; scenarios cover real life. Guiding
  constraint: minimize new scope — fix, test, verify what exists; prefer
  deleting over adding.
• Coordination: GitHub Issues are the unit of work; the
  LifeOps Personal Assistant MVP board (project 15)
  is the live queue; Discussions carry design conversation (one kickoff per
  workstream in General + one pinned master thread in Announcements);
  packages/docs/ongoing-development/ is the source of truth for in-flight
  product thinking. Flow: discussion → design doc → issues on board 15 → PR
  with inline evidence → doc updated. A decision that only lives in a
  discussion comment is not a decision — PR it into a doc.
• Evidence is posted inline in the issue/PR — the repo-committed
  .github/issue-evidence/ directory is retired. Videos are MP4 (GitHub
  renders MP4 inline; convert with
  ffmpeg -i in.mov -c:v libx264 -pix_fmt yuv420p out.mp4). Screenshots are
  JPG where possible (smaller than PNG). Long logs go in <details>
  blocks. If a video can't fit GitHub's upload cap, host it, link it, and keep
  a representative JPG still inline. Bug reports must show the wrong
  behavior (JPG/MP4) or they are not actionable. Full standard:
  PR_EVIDENCE.md; mechanical gate: scripts/check-pr-evidence.mjs via
  .github/workflows/pr.yaml.

Research doc

packages/docs/ongoing-development/research/09-doc-driven-development.md —
current state with file:line evidence, decisions on every open question
(including: no PNG-lint CI check, no grace period for retired evidence paths,
discussion category mapping), the ordered plan, and ready-to-apply appendices
(the ongoing-development README, the MVP stub, the evidence-gate edit spec).

Issues in this workstream (board 15, most important first)

1. [process] Create packages/docs/ongoing-development README + MVP stub (fixes red markdown-links lane) — P0
2. [process] check-pr-evidence: stop accepting retired .github/issue-evidence paths — P1
3. [process] Migrate the 3 residual .github/issue-evidence files to comments on their closed issues — P1
4. [process] Sweep 546 per-package CLAUDE.md/AGENTS.md evidence lines to inline-attachment guidance — P1
5. [process] Open the MVP coordination discussions (master thread + per-workstream kickoffs) — P1
6. [process] Repoint CI/scripts scratch paths off .github/issue-evidence and delete the broken benchmark-history workflow — P2
7. [process] Restore docs/automation-glossary.md deleted by the evidence purge — P2

How to claim work

1. Comment on the issue: what you'll do and roughly how.
2. Move its card on
   board 15 to In Progress.
3. One card per agent at a time. Don't start unboarded MVP work — file the
   issue first.
4. PR against develop, branch feat|fix|docs|chore/<slug>, rebased and
   conflict-free (git fetch origin && git rebase origin/develop).

Evidence rules for PRs in this workstream

Every PR fills the evidence rows in the PR template — attached inline, or
N/A - <reason> on the row, never blank:

• MP4 walkthrough for anything a user can see or click.
• JPG before + after screenshots (desktop and mobile) for UI; bugs include
  the wrong behavior.
• Logs ([ClassName] … backend, console/network frontend) in <details>.
• Real-LLM trajectory when agent/action/prompt/model behavior changes.
• Most issues in this workstream are docs/CI — terminal logs of the relevant
  checkers (scripts/check-markdown-links.mjs,
  scripts/check-pr-evidence.mjs --self-test, bun run check:agents-claude)
  before and after are the required proof, pasted inline.

If your change moves the process itself, update
packages/docs/ongoing-development/research/09-doc-driven-development.md in
the same PR. A stale design doc is a bug.

Filed issues

• [process] check-pr-evidence: stop accepting retired .github/issue-evidence paths #14340 — P1 [process] check-pr-evidence: stop accepting retired .github/issue-evidence paths
• [process] Sweep 546 per-package CLAUDE.md/AGENTS.md evidence lines to inline-attachment guidance #14341 — P1 [process] Sweep 546 per-package CLAUDE.md/AGENTS.md evidence lines to inline-attachment guidance
• [process] Repoint CI/scripts scratch paths off .github/issue-evidence and delete the broken benchmark-history workflow #14342 — P2 [process] Repoint CI/scripts scratch paths off .github/issue-evidence and delete the broken benchmark-history workflow

---

Design doc · MVP board