ARCHIVE-03: Dogfooding sprint - 10+ days of real personal use as the pivot's acceptance test

[Chris0Jeky]

Context

Seeded by the 2026-07-02 whole-project analysis (docs/COURSE_CORRECTION.md). Verified: zero organic personal-work data exists anywhere. The canonical dev DB (%LOCALAPPDATA%\Taskdeck\taskdeck-dev.db) contains 4 DEMO boards and 11 cards seeded in a 19-second window on 2026-07-02, plus one bare "chris" registration with zero content and onboarding never completed. The Api-folder DB has DEMO + manual smoke-test boards last touched 2026-04-23; the repo-root DB has 0 boards. The strategy doc's "Start daily dogfooding cadence" checkbox is unchecked and no issue tracked dogfooding until this one.

"Finished for personal use" is unverifiable without personal use — and real use is the cheapest, most accurate issue-generator available for aiming the remaining quality work. This task is the acceptance test for the entire pivot and cannot be delegated to agents.

Acceptance criteria

• Maintainer manages real work (obvious seed: this repo's own OUTSTANDING_TASKS and ARCHIVE-wave items) through capture → triage → review → apply, daily, starting immediately and running in parallel with the truth fixes (GetProposalDiffAsync ignores saved ProposalRevisions — preview diff can mislead when an edit is pending #1235, ARCHIVE-04, ARCHIVE-05) that land in the first days.
• ≥10 working days of organic (non-DEMO) boards/cards/captures exist in %LOCALAPPDATA%\Taskdeck.
• Friction/defects surfaced are triaged against the ARCHIVE-01 severity bar (dogfooding findings are exempt from the intake freeze) and either fixed or dated-accepted.
• A short dated usage report lands in STATUS.md (or the exit-criteria doc) as acceptance evidence for ARCHIVE-09, and the dogfooding-cadence checkbox is checked.