Deferred work

Items that came up during Tasksets 1–8 and were intentionally deferred to a future taskset rather than absorbed in scope. Per MR-2, deferred friction is next-phase input, never retrofitted.

From TASKSET 5 (write verbs)

• Live --apply integration tests against a sandbox repo. Requires PAT or GitHub App credentials. The dry-run path is fully tested; the apply path is structurally complete but unexercised against real GitHub.
• Branch-protection precondition check for request_merge_when_green. Currently relies on enableAutoMerge failing gracefully if protection isn’t configured. Should harden to an explicit pre-check.

From TASKSET 7 (KAHN integration)

• Live --apply against kahn-hq. First true cross-repo fleet write. Requires PAT + a non-trivial real change worth opening a PR for.
• Updating kahn-hq’s local AGENTS.xml to declare the petrova-act capability. Could be done via petrova request_review kahn-hq.
• smo1-io registration. Workspace dir exists but isn’t a git repo locally; defer until origin URL is known.

From the original design (Stream 4 scope)

• Webhook receiver. Push-based fleet reactions to PR events. Build only when polling demonstrably falls short.
• SQLite cache. Local cross-repo index for sub-second queries. Add only when GitHub rate limits bite or full-fleet diagnostics become slow.
• Web UI dashboard. A persistent rendered version of petrova dashboard. Add only when CLI output becomes insufficient (e.g. a team needs read-only access to fleet status).

From this taskset (Increment A)

• Hand-authored prose pages (Increment B): OVERVIEW (4), CONCEPTS (9), ARCHITECTURE (5), CLI auth + config (2). ~20 pages.
• Cross-reference link checker in CI (Increment C).
• Verification of all 7 end-to-end checks (Increment C).