[codex] Record v0.2 alpha closure decision

docs/public-readiness.md

@@ -7,7 +7,8 @@ Current status: the repository is public and the v0.2 alpha release train is
 gated through `release-ticket`, `release-status`, and the GitHub Actions
 `audit` job. Treat the older checkbox lists below as reusable release hygiene,
 not as the sole source of truth for current alpha readiness. The current
-reviewer bundle is:
+closure decision is [`docs/v0.2-alpha-closure.md`](v0.2-alpha-closure.md), and
+the current reviewer bundle is:
 
 ```sh
 cargo run --locked -- release-ticket --out dist/release-ticket --force --json

docs/v0.2-alpha-closure.md

@@ -0,0 +1,76 @@
+# AgentK v0.2 Alpha Closure Decision
+
+Date: 2026-06-05
+
+## Decision
+
+AgentK v0.2 alpha is ready to stop feature expansion as an installable
+local/team sidecar release candidate.
+
+The alpha claim is intentionally narrow: AgentK is an MCP action firewall and
+flight recorder that a team can install locally, put in front of Claude, Codex,
+Cursor, or another MCP client, and use to review redacted approvals, audit
+evidence, permissions, durable store exports, notification handoffs, deployment
+templates, support bundles, and the credential-free safe-agent demo.
+
+## Evidence To Keep
+
+The current release train is gated by:
+
+- `cargo run --locked -- release-status --json`
+- `cargo run --locked -- release-ticket --out dist/release-ticket --force --json`
+- `cargo run --locked -- release-audit`
+- GitHub Actions `audit` on merged pull requests
+
+At closure, `release-status --json` reports `ready_for_alpha_rc: true` and the
+following shipped surfaces as passing:
+
+- installable team sidecar package
+- bounded local MCP gateway adapters
+- approvals and audit dashboard
+- multi-user permissions and identity mappings
+- durable audit store and notification bridges
+- safe-agent demo package path
+- team approval/audit handoff package path
+- support bundle package path
+- deploy handoff package path
+- local Homebrew formula handoff
+
+The release ticket also checks the product objectives directly:
+
+- production MCP gateway evidence for the bounded local gateway handoff
+- approvals/audit dashboard evidence
+- multi-user permissions evidence
+- Claude/Codex/Cursor sidecar evidence, including the actual Claude MCP JSON
+  and Codex/Cursor command file
+- safe-agent demo evidence across GitHub/Postgres/Slack/filesystem, including
+  local bridge dry-runs and blocked filesystem patch proof
+
+## Accepted Alpha Limits
+
+These are not hidden failures. They are intentionally deferred from v0.2 alpha:
+
+- hosted SaaS control plane
+- public internet MCP gateway, TLS termination, and hosted SSE streaming
+- live IdP/OIDC/JWT authentication
+- production secret retrieval
+- hosted ticketing integrations
+- OS sandboxing, eBPF, cgroups, and kernel/filesystem isolation
+
+The alpha remains useful without those because it proves the local/team sidecar
+workflow end to end and keeps broader production claims out of the release.
+
+## Stop Rule
+
+For this automation run, stop adding new product surface once the closure note,
+release-status, release-ticket, release-audit, and GitHub Actions audit are
+green on `master`.
+
+Next work should start from one explicit post-alpha theme rather than continuing
+the current broad productization push. Recommended candidates are:
+
+- public internet/TLS deployment hardening
+- live IdP authentication
+- production secret-manager retrieval
+- hosted/team service architecture
+

docs/v0.2-alpha-release-notes.md

@@ -5,6 +5,9 @@ not final release evidence until the release commit, strict release-audit
 result, package archive checksum, package release manifest, signed tag
 verification, and signer evidence are filled in.
 
+The current stop/ship decision for this alpha train is recorded in
+[`docs/v0.2-alpha-closure.md`](v0.2-alpha-closure.md).
+
 ## Summary
 
 AgentK v0.2 alpha turns the v0.1 public prototype into an installable local