docs(automations): record Coven Automations v1 program status (coven#854)

[CompleteDotTech]

Summary

• Adds one dated status/decision record for the Coven Automations v1 program in the repo's record location: docs/superpowers/plans/2026-08-30-coven-automations-v1-program-status.md.
• Independently verifies, against main @ 1364cec (2026-08-30), that the coven#816 foundation series (PR feat(automations): routine definitions and control actions (coven#816, part 1) OpenCoven/coven#846 merged 2026-08-28T14:22:30Z, PR feat(automations): non-destructive legacy Codex import (coven#816, part 5) OpenCoven/coven#847 merged 2026-08-28T19:55:52Z, parts 6–8 commits dated 2026-08-28) landed the durable local scheduler core: versioned definitions, SQLite definition/occurrence/run records, unique occurrence fencing (UNIQUE(automation_id, scheduled_for)), RRULE planning, bounded leases with expiry/recovery, latest-only misfire and overlap refusal, the 60s daemon tick with scheduled dispatch, the shared launch path, familiar-id propagation, health/run-history projections, non-destructive paused legacy import, and the 10 coven.automations.* control actions (11 files, 2,719 lines, 43 unit tests).
• Confirms what is absent for v1: no coven.automations.v1 schemas/spec/state machines (P0: Specify coven.automations.v1 schemas, state machines, idempotency, and changefeed OpenCoven/coven#855), fixed wall-clock cadence with no DST/virtual-time/clock-jump/fencing contract (P0: Harden automation time, retries, cancellation, fencing, and crash recovery OpenCoven/coven#856), optional unversioned familiar_id with no principal/capability/approval/receipt binding (P0: Bind automation runs to principal authority, familiar revisions, capabilities, approvals, and receipts OpenCoven/coven#857), no conformance/chaos/load/SLO or release-receipt gate (P0: Build automations conformance, chaos, SLO, and operator diagnostics OpenCoven/coven#858), no SDK surface and no live Beads-graph mutation (coven-cave#5220).
• Records the gate-by-gate verdict (A partial, B/C/D not met / partial) against the issue's definition of done and pins the critical path: coven-cave#5220/P0 control: Operationalize Coven Automations v1 through Cave’s canonical Beads graph and GitHub mirrors OpenCoven/coven#859 → Native familiar automations: replace harness-owned schedules with durable Coven routines OpenCoven/coven#816 evidence closure → P0: Specify coven.automations.v1 schemas, state machines, idempotency, and changefeed OpenCoven/coven#855 → P0: Harden automation time, retries, cancellation, fencing, and crash recovery OpenCoven/coven#856 + familiar-contract#17 + coven-threads#29 → P0: Bind automation runs to principal authority, familiar revisions, capabilities, approvals, and receipts OpenCoven/coven#857 → P0: Build automations conformance, chaos, SLO, and operator diagnostics OpenCoven/coven#858 → SDK/Cave/Psyche/docs/.github → exact-release go/no-go packet.
• Decision: Program: Coven Automations v1 — reliable, identity-bound familiar routines OpenCoven/coven#854 remains open. This record closes no issue; it unblocks Native familiar automations: replace harness-owned schedules with durable Coven routines OpenCoven/coven#816's evidence-closure item and P0 control: Operationalize Coven Automations v1 through Cave’s canonical Beads graph and GitHub mirrors OpenCoven/coven#859's tracker-mapping task.

Issue

Refs OpenCoven#854.

Intentionally Refs rather than Closes: the record's verified verdict is "foundation-ready, not yet v1-certified" — the program issue stays open until the P0 gates are implemented and evidenced, so merging this docs record must not auto-close it.

Test plan

Local (docs-only change, no code touched):

• Deconfliction sweep clean before starting: upstream PR search, open-PR list, and fork branches contain no existing Program: Coven Automations v1 — reliable, identity-bound familiar routines OpenCoven/coven#854 work (REST, 2026-08-30 ~15:08 UTC).
• Every file/line/commit/PR/issue citation in the record re-verified against main @ 1364cec and REST issue state before commit.
• Markdown renders as a standard GitHub doc (tables, relative code refs; no links to private state).

Deferred to CI (python3 is not available in the local environment):

• python scripts/check-secrets.py
• python3 scripts/check-coven-privacy.py --staged

Not applicable locally: cargo/npm gates — the diff touches only one Markdown file, and this environment has no Rust toolchain; CI's changes classifier should route this PR as docs-only.

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#854.

CI note (2026-08-30): this fork vehicle has no CI — zero check runs exist for the head commit and zero workflow runs exist repo-wide ~12 minutes after opening, although Actions is enabled (allowed_actions: all) and .github/workflows/ci.yml declares a pull_request trigger. Nothing to watch; per the task CI contract the PR proceeds with no checks. The real verification gates live in upstream OpenCoven/coven CI, which this token could not target (PR creation returned 403). Note: the PR reports draft: false although it was created with --draft; draft state cannot be changed via REST and GraphQL is reserved for the single sanctioned flip call.