docs: address bot review findings on PR #764

- AGENTS.md: add $LASTEXITCODE fail-fast checks to PowerShell command
  chain (Gemini + Copilot finding)
- TESTING_GUIDE.md: clarify telemetry taxonomy is "documented" not
  "delivered" (spec exists, instrumentation not shipped); fix
  proposal.dismissed → proposal.rejected (matches actual taxonomy)
- STATUS.md: annotate stale frontend unit count (1491) with pointer
  to latest estimate (1592) in TESTING_GUIDE.md

Author: Chris0Jeky

AGENTS.md

@@ -100,7 +100,7 @@ Its scope applies to the entire repo unless overridden by more specific `AGENTS.
 - Backend API (local): from `backend/src/Taskdeck.Api`, run `dotnet run`.
 - Frontend dev server: from `frontend/taskdeck-web`, run `npm install` once, then `npm run dev`.
 - Frontend checks (required when frontend touched): from `frontend/taskdeck-web`,
-  `npm run typecheck ; npm run build ; npx vitest --run` (use `;` not `&&` in PowerShell).
+  `npm run typecheck; if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }; npm run build; if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }; npx vitest --run` (PowerShell fail-fast; do not use `&&`).
 
 ## Coding Style & Naming
 - Backend: C# conventions, 4-space indentation, PascalCase for classes and public members,

docs/STATUS.md

@@ -781,7 +781,7 @@ Commands:
 - `cd frontend/taskdeck-web && npm run build`
 
 Result:
-- Frontend unit: 1491/1491 passing (134 test files)
+- Frontend unit: 1491/1491 passing (134 test files) — **stale**: post-wave count is 1592/1592 (~125 files); see `docs/TESTING_GUIDE.md` for latest estimates
 - Typecheck: passing
 - Production build: passing
 

docs/TESTING_GUIDE.md

@@ -51,8 +51,8 @@ High-signal additions and delivered guardrails:
 
 Telemetry and release-gate follow-through from the expanded blueprint:
 
-- product telemetry/event taxonomy delivered in `#341`/`#741` — see `docs/product/TELEMETRY_TAXONOMY.md`; reuses `#77` as baseline; `#328` provides the delivered first-run guardrail
-- keep event names privacy-safe and product-shaped using the canonical `noun.verb` format from `docs/product/TELEMETRY_TAXONOMY.md` (for example `capture.modal_opened`, `capture.submitted`, `proposal.approved`, `proposal.dismissed`, `card.created`, `board.loaded`, `auth_session.started`, `agent_run.completed`, `agent_run.failed`)
+- product telemetry/event taxonomy documented in `#341`/`#741` — see `docs/product/TELEMETRY_TAXONOMY.md` (taxonomy spec, not shipped instrumentation); reuses `#77` as baseline; `#328` provides the delivered first-run guardrail
+- keep event names privacy-safe and product-shaped using the canonical `noun.verb` format from `docs/product/TELEMETRY_TAXONOMY.md` (for example `capture.modal_opened`, `capture.submitted`, `proposal.approved`, `proposal.rejected`, `card.created`, `board.loaded`, `auth_session.started`, `agent_run.completed`, `agent_run.failed`)
 - treat launch framing as evidence gates, not marketing labels:
   - `R1` novice-first beta -> coherent `Home -> capture -> review -> execute -> board` path
   - `R2` agent foundation alpha -> inspectable runs, policies, and bounded templates