docs(807): record shipped reliability scorecard status decision

[CompleteDotTech]

Context

• Summary: Adds one dated status/decision record for issue P1: establish Coven shipped reliability, recovery, and usefulness scorecard OpenCoven/coven#807 (P1: establish Coven shipped reliability, recovery, and usefulness scorecard) in the repo's existing record location (docs/superpowers/plans/), per the issue's requirement that observed outcomes, targets, and benchmark inputs stay visibly distinct. The record documents, with evidence links and dates at main @ 1364cec9 (2026-08-30): the existing non-gating benchmark/chaos corpus (scripts/benchmark-cli.mjs, scripts/benchmark-chaos.mjs, artifact-only CI collection), health/readiness/recovery surfaces (GET /api/v1/health storage object, coven doctor, --verify-only --report-json), release certification (scripts/certify-release.sh, added 2026-08-29), packaged-artifact journey E2E (scripts/user-journey-e2e.mjs, updated 2026-08-28), the release-stress workflow (added 2026-08-24), and the AFS feature-gated posture; then gives a row-by-row verdict against all six acceptance criteria (not satisfied on main; no scorecard exists — grep for scorecard returns 0 hits) and a dependency-ordered critical path. It invents no measurements, targets, or SLOs, consistent with the issue's non-goals.
• Files changed: docs/superpowers/plans/2026-08-30-issue-807-shipped-reliability-scorecard.md (new, +172)
• Refs P1: establish Coven shipped reliability, recovery, and usefulness scorecard OpenCoven/coven#807

Implementation

• Approach: Documentation-only record; investigation performed against upstream main at commit 1364cec9 ("chore: preserve consolidated branch ancestry", 2026-08-30). Evidence gathered via REST-only GitHub API (issues, releases, release-by-tag, search) plus local inspection of the clone; every claim in the record carries a permalink (8-char SHA, matching the convention of existing plan records) or a file/commit reference with a date.
• User-visible behavior: None (no code or product surface changes; one new planning record).
• Compatibility notes: None. scripts/classify-ci-changes.py routes docs-only changes away from the Rust/npm matrix.

Verification

• cargo fmt --check — deferred to CI (docs-only change; Rust untouched)
• cargo clippy --workspace --all-targets -- -D warnings — deferred to CI (docs-only change)
• cargo test --workspace --locked — deferred to CI (docs-only change)
• python3 scripts/check-secrets.py — passed locally (initial draft tripped the entropy rule on full-SHA GitHub URLs; fixed by adopting the repo's existing 8-char short-SHA link convention, then re-run clean)
• python3 scripts/check-coven-privacy.py --staged — passed locally
• git diff --check — clean
• Additional manual checks: REST-only API discipline held (no GraphQL); deconfliction per issue P1: establish Coven shipped reliability, recovery, and usefulness scorecard OpenCoven/coven#807 Step 0 (no open PR or branch for P1: establish Coven shipped reliability, recovery, and usefulness scorecard OpenCoven/coven#807 at 2026-08-30); local node/pnpm toolchain available but unused (no package surface touched)
• Additional manual checks: CI note — no CI exists in this fork vehicle. After ~10 minutes with the PR open, GET /repos/CompleteDotTech/coven/commits/8cc6c4a6c75f55f7c701e1d6b58d3b47efaa2f11/check-runs returned total_count: 0, the repo's workflow-run list is empty (total_count: 0 — no run has ever been created here, nothing stuck queued/waiting), and repo Actions report enabled: true with all workflows present on main. The upstream pull_request trigger in ci.yml is unconditional, so the absence is a fork-runner property, not a path filter. Nothing is claimed green; the docs-only local checks above are the verification record.

Risk and Rollback

• Risk level: Low — additive docs-only record; no runtime surface, no CI-gate behavior change.
• Rollback plan: Revert the single commit (removes only the new file).

Agent Handoff

• Current state: Record landed on the agent branch; CI verdict pending at open time.
• Follow-ups: The record's "What remains" section lists the dependency-ordered critical path: create the scorecard itself with the five row labels, attach the metric contract per row, wire structured receipts from certify-release.sh/user-journey-e2e.mjs/benchmark collectors, raise benchmark sample counts before quoting p95/p99, then release-quality rows after P0: enforce exact-commit release governance and shipped-truth attestation OpenCoven/coven#805/test: certify Coven end-to-end from packaged artifact through recovery and release evidence OpenCoven/coven#779 land.
• Known gaps: No scorecard document exists on main yet; usefulness/outcome rows have no measurement instrument by design (no opt-in telemetry exists, and the issue forbids inventing adoption targets).

Vehicle note: opened in the fork CompleteDotTech/coven as the CI vehicle — this token cannot write to OpenCoven/coven. Re-target upstream once write access is restored. Refs OpenCoven#807.