docs: add honcho redis auto-deploy noop probe #242

Merged

pdurlej merged 1 commit from codex/auto-deploy/honcho-redis-noop-probe into main

2026-05-12 08:08:07 +02:00

codex commented

2026-05-12 08:04:24 +02:00

Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Canary Context Pack

Product story

This is the first deliberate no-op probe for the PM-safe auto-deploy lane: Piotr merges a harmless runbook-only change, and the trusted post-merge pipeline should plan, apply as noop, run health, and upload evidence for honcho-redis.

What changed

Added a short ## Auto-deploy probe section to modules/honcho-redis/runbook.md.

Why it changed

We need one low-risk module change to prove the future “click Merge → evidence appears” workflow before any runtime-changing deploy.

Files touched

modules/honcho-redis/runbook.md

Relevant context

#234 adds the active platformctl auto-apply skeleton and scope classifier.
#241 adds the canonical compose candidate.
honcho-redis is rs2000, docker-compose, relative compose/apps/compose.yaml, and eligible for the v1 auto-apply allowlist.

Runtime evidence

No RS2000 runtime mutation from this PR.

Scope check run using the #234 classifier against this branch:

{
  "status": "eligible",
  "safe_to_apply": true,
  "allowed_modules": ["honcho-redis"],
  "blocked_modules": [],
  "changed_files": ["modules/honcho-redis/runbook.md"]
}

Checks run:

git diff --check
PYTHONPATH=control-plane python3 /tmp/auto_apply_scope.py --repo-root "$PWD" --base origin/main --head HEAD --json /tmp/honcho-redis-probe-scope.json --markdown /tmp/honcho-redis-probe-scope.md --fail-on-blocked

Known constraints

This PR only proves the E2E path if merged after #234 is on main and the deploy-host runner is configured. If merged earlier, it is just a harmless docs change.

Explicit out-of-scope

No Redis config change.
No compose change.
No service restart requested by this PR.
No production mutation before the trusted main workflow runs.

Requested decision

Merge this only as the first auto-deploy no-op E2E probe after #234/#241 and deploy-host setup are complete.

Merge blockers

#234 not merged.
rs2000-deploy-host / deploy-host not configured.
Operator is not ready to watch the first auto-apply evidence artifact.

Operator Merge Checklist

Merge #233, #234, #239, and #241 first.
Confirm the dedicated deploy-host runner is configured and branch protection is active.
Then merge this PR as the first no-op E2E probe.
After merge, ask Codex to verify the auto-apply artifact and health result.

Spec sources read

modules/honcho-redis/module.yaml — auto-apply allowlist eligibility.
modules/honcho-redis/runbook.md — edited file.
#234 classifier script via branch artifact — scope eligibility check.

Refs #142
Refs #220

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story This is the first deliberate no-op probe for the PM-safe auto-deploy lane: Piotr merges a harmless runbook-only change, and the trusted post-merge pipeline should plan, apply as `noop`, run health, and upload evidence for `honcho-redis`. ### What changed Added a short `## Auto-deploy probe` section to `modules/honcho-redis/runbook.md`. ### Why it changed We need one low-risk module change to prove the future “click Merge → evidence appears” workflow before any runtime-changing deploy. ### Files touched - `modules/honcho-redis/runbook.md` ### Relevant context - #234 adds the active `platformctl` auto-apply skeleton and scope classifier. - #241 adds the canonical compose candidate. - `honcho-redis` is `rs2000`, `docker-compose`, relative `compose/apps/compose.yaml`, and eligible for the v1 auto-apply allowlist. ### Runtime evidence No RS2000 runtime mutation from this PR. Scope check run using the #234 classifier against this branch: ```json { "status": "eligible", "safe_to_apply": true, "allowed_modules": ["honcho-redis"], "blocked_modules": [], "changed_files": ["modules/honcho-redis/runbook.md"] } ``` Checks run: ```bash git diff --check PYTHONPATH=control-plane python3 /tmp/auto_apply_scope.py --repo-root "$PWD" --base origin/main --head HEAD --json /tmp/honcho-redis-probe-scope.json --markdown /tmp/honcho-redis-probe-scope.md --fail-on-blocked ``` ### Known constraints This PR only proves the E2E path if merged after #234 is on `main` and the `deploy-host` runner is configured. If merged earlier, it is just a harmless docs change. ### Explicit out-of-scope - No Redis config change. - No compose change. - No service restart requested by this PR. - No production mutation before the trusted main workflow runs. ### Requested decision Merge this only as the first auto-deploy no-op E2E probe after #234/#241 and deploy-host setup are complete. ### Merge blockers - #234 not merged. - `rs2000-deploy-host` / `deploy-host` not configured. - Operator is not ready to watch the first auto-apply evidence artifact. ## Operator Merge Checklist 1. Merge #233, #234, #239, and #241 first. 2. Confirm the dedicated `deploy-host` runner is configured and branch protection is active. 3. Then merge this PR as the first no-op E2E probe. 4. After merge, ask Codex to verify the auto-apply artifact and health result. ## Spec sources read - `modules/honcho-redis/module.yaml` — auto-apply allowlist eligibility. - `modules/honcho-redis/runbook.md` — edited file. - #234 classifier script via branch artifact — scope eligibility check. Refs #142 Refs #220

codex added 1 commit

2026-05-12 08:04:24 +02:00

docs: add honcho redis auto-deploy noop probe

canary-required / collect-diff (pull_request) Successful in 4s

Details

canary-required / canary (pull_request) Successful in 12s

Details

base-is-main / guard (pull_request) Successful in 1s

Details

612fe4d824

codex added the

class/security-sensitive