jb/eden
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record unverified runner boundary

Browse Source
This commit is contained in:
jb
2026-09-19 10:01:23 -04:00
parent 5b0076cb20
commit 99fe7e1ca2
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/release-safety.md
+8 -3
View File
@@ -114,9 +114,14 @@ locally but has not run remotely. The source job runs a strict staging release
check after building the client. The separate container job is currently check after building the client. The separate container job is currently
**disabled** (`if: ${{ false }}`), not merely push-filtered: its rootless **disabled** (`if: ${{ false }}`), not merely push-filtered: its rootless
runner and protected-ref policy require operator verification and approval runner and protected-ref policy require operator verification and approval
before enablement. Its draft commands use per-run image, volume, and container before enablement. The local infrastructure plan mentions `personal-isolated`,
names and clean up only those names, but are not release evidence while the job `ubuntu-latest`, and `ubuntu-22.04` labels, but those are not confirmed
is disabled. No browser automation, OAuth callback failure injection, Convex registered labels. The plan describes a dedicated runner VM with a
Docker-socket-backed daemon; rootless execution, online status, action
availability, and protected refs remain unverified. Its draft commands use
per-run image, volume, and container names and clean up only those names, but
are not release evidence while the job is disabled. No browser automation,
OAuth callback failure injection, Convex
migration rollback, instance-credential backup/restore, key rotation, or live migration rollback, instance-credential backup/restore, key rotation, or live
revocation/transfer evidence is claimed by this lane. Those remain explicit revocation/transfer evidence is claimed by this lane. Those remain explicit
operator/integration gates and must use synthetic or separately consented operator/integration gates and must use synthetic or separately consented