Skip to content

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

docs: the human publish gate is the dashboard click, not tag protection (#6096)

Louis Beaumont3b67d78e55ed
diff --git a/AGENTS.md b/AGENTS.md
index 925687db4..cdf244dcc 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -62,7 +62,7 @@ This will help maintainers review and ultimately resolve and merge contributions
## app publication boundary
- AI agents may bump versions, push source, build, sign, notarize, and upload immutable versioned app/enterprise artifacts.
-- AI agents must never update `latest.json`, `beta/latest.json`, or `enterprise/published.json`; create `app-v*` / `app-beta-v*` tags or GitHub releases; disable/bypass the `Human-only app publication tags` ruleset; approve the `app-publication` environment; or invoke the admin publication endpoint.
+- AI agents must never update `latest.json`, `beta/latest.json`, or `enterprise/published.json`; create `app-v*` / `app-beta-v*` tags or GitHub releases; weaken the `Human-only app publication tags` ruleset (its repository-`admin` bypass exists so the human dashboard publish can create its own tag — removing it blocks publication, it does not harden it); approve the `app-publication` environment; or invoke the admin publication endpoint.
- Public app publication is a human action performed from the authenticated admin releases UI after reviewing the exact version, commit, CI, and artifact set.
- Release automation receives only `RELEASE_UPLOAD_TOKEN`, whose server-side capability is limited to `releases/<version>/<target>/<artifact>` and `enterprise/releases/<version>/<target>/<artifact>`.
diff --git a/docs/human-only-app-publication.md b/docs/human-only-app-publication.md
index 46fa791c6..01243a13c 100644
--- a/docs/human-only-app-publication.md
+++ b/docs/human-only-app-publication.md
@@ -20,11 +20,13 @@ Public publication includes any of the following:
- creating an `app-v*` or `app-beta-v*` tag or GitHub release;
- notifying subscribers or announcing availability.
-GitHub ruleset `Human-only app publication tags` denies app publication-tag creation, update, and deletion by default. Environment `app-publication` requires Louis as reviewer, prevents self-review, and does not allow administrator bypass.
+The human gate is the click. The authenticated releases control in the website admin UI is the only publication path: it requires an internal `releases:write` permission plus Clerk reverification, and it is the single action that writes updater pointers, creates the GitHub release, and dispatches the changelog. Before clicking, the human verifies the exact bump commit, required CI, all signed platform artifacts, and the intended channel.
-The human publication path is the authenticated releases control in the website admin UI. Before publishing, the human must verify the exact bump commit, required CI, all signed platform artifacts, and the intended channel. If a stable GitHub release is required, the human temporarily changes the tag ruleset in GitHub's web settings, publishes from the admin UI, verifies the release, and immediately restores the ruleset to active enforcement.
+Automation cannot reach that path because the release workflows hold no publication credentials at all: `076735b17` removed them, leaving `Release App` and `Release Enterprise` with only the artifact-uploader service described above. Credential scoping, not tag protection, is what keeps publication human-only.
-AI agents must not operate the admin UI, call its publication endpoint, approve the environment, or disable/bypass the tag ruleset.
+GitHub ruleset `Human-only app publication tags` protects `app-v*` and `app-beta-v*` against creation, update, and deletion, and bypasses the repository `admin` role so the dashboard's own publish can create its tag. It is a guard against stray write-scoped tokens, not the human gate. Do not remove the bypass: doing so blocks the dashboard itself, which is exactly what silently stopped every GitHub release between `app-v2.5.176` and `2.6.0` while `latest.json` kept shipping. Environment `app-publication` requires Louis as reviewer, prevents self-review, and does not allow administrator bypass.
+
+AI agents must not operate the admin UI, call its publication endpoint, approve the environment, or weaken the tag ruleset.
## Emergency stop