pdurlej/platform

Fork 0

docs(honcho): record host-ops env cleanup #778

Merged

pdurlej merged 1 commit from codex/honcho-host-ops-env-cleanup-record into main

2026-06-17 23:02:34 +02:00

codex commented

2026-06-10 22:32:51 +02:00

Collaborator

Canary status: missing - fire canary manually if required by repo policy

Context

Runtime cleanup was performed on rs2000 after PR #777 codified the Honcho 3.0.9 host-ops state. This PR records the cleanup evidence and closes the follow-up left in the 3.0.9 reconcile report.

What changed

Added state/reports/honcho-host-ops-env-cleanup-2026-06-10.md.
Updated state/reports/honcho-309-host-ops-reconcile-2026-06-10.md to point at the completed cleanup report.

Runtime change already applied

Active file:

/opt/pdurlej-platform/runtime/host-ops/env/stack.env

Changes:

PROJECT_ROOT now points to /opt/pdurlej-platform/current.
Removed stale HONCHO_IMAGE=home-platform-honcho:3.0.3.
Removed stale HONCHO_IMAGE_REF=v3.0.3.

No container restart or recreate was performed.

Evidence

Backup created: /opt/pdurlej-platform/runtime/host-ops/env/stack.env.pre-honcho-cleanup-20260610T2035Z.
Post-cleanup key check returned only PROJECT_ROOT=/opt/pdurlej-platform/current for the targeted keys.
home-platform-honcho-api-1: 3.0.9 image, running, healthy, restarts=0.
home-platform-honcho-deriver-1: 3.0.9 image, running, healthy, restarts=0.
https://honcho.pdurlej.com/openapi.json returned HTTP 200.

Verification

git diff --cached --check
Secret-pattern scan over touched reports: no matches.

Out of scope

Any deploy, restart, recreate, database migration, secret change, or public exposure change.
Long-term decision on whether Honcho image pinning should be env-driven or literal in compose.

Refs #731

Canary status: missing - fire canary manually if required by repo policy ## Context Runtime cleanup was performed on `rs2000` after PR #777 codified the Honcho 3.0.9 host-ops state. This PR records the cleanup evidence and closes the follow-up left in the 3.0.9 reconcile report. ## What changed - Added `state/reports/honcho-host-ops-env-cleanup-2026-06-10.md`. - Updated `state/reports/honcho-309-host-ops-reconcile-2026-06-10.md` to point at the completed cleanup report. ## Runtime change already applied Active file: ```text /opt/pdurlej-platform/runtime/host-ops/env/stack.env ``` Changes: - `PROJECT_ROOT` now points to `/opt/pdurlej-platform/current`. - Removed stale `HONCHO_IMAGE=home-platform-honcho:3.0.3`. - Removed stale `HONCHO_IMAGE_REF=v3.0.3`. No container restart or recreate was performed. ## Evidence - Backup created: `/opt/pdurlej-platform/runtime/host-ops/env/stack.env.pre-honcho-cleanup-20260610T2035Z`. - Post-cleanup key check returned only `PROJECT_ROOT=/opt/pdurlej-platform/current` for the targeted keys. - `home-platform-honcho-api-1`: 3.0.9 image, running, healthy, `restarts=0`. - `home-platform-honcho-deriver-1`: 3.0.9 image, running, healthy, `restarts=0`. - `https://honcho.pdurlej.com/openapi.json` returned HTTP 200. ## Verification - `git diff --cached --check` - Secret-pattern scan over touched reports: no matches. ## Out of scope - Any deploy, restart, recreate, database migration, secret change, or public exposure change. - Long-term decision on whether Honcho image pinning should be env-driven or literal in compose. Refs #731

codex added the

labels

2026-06-10 22:32:51 +02:00

codex added 1 commit

2026-06-10 22:32:51 +02:00

docs(honcho): record host-ops env cleanup

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

Details

canary-required / canary (pull_request) Has been skipped

Details

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

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s

Details

patchwarden-client-dry-run / dry-run (pull_request) Successful in 29s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 47s

Details

1d2d1921c8

patchwarden commented

2026-06-10 23:06:00 +02:00

First-time contributor

No Patchwarden findings to render.

patchwarden commented

2026-06-10 23:08:10 +02:00

First-time contributor

Patchwarden PR sanity

Status: eligible_sanity_clean
PR: 778
Commit: 1d2d1921c83c2cdb1c14dda26cb7f0c6c0b5d48d
Security-sensitive label: missing
Authority: advisory model review plus deterministic blockers only
3+3 canary: still alive; this does not replace it

Deterministic findings

No deterministic findings.

Model reviewers

`global-glm` / `glm-5.1:cloud`

Status: ok
Verdict: OK
Findings: none

`global-deepseek` / `deepseek-v4-pro:cloud`

Status: ok
Verdict: OK
low Missing canary for docs-only PR
- Evidence: PR description states 'Canary status: missing - fire canary manually if required by repo policy'. The PR is documentation-only, but if the repository enforces canary for all merges, this may be a process gap.
- Next: Confirm whether the repo policy requires a canary for documentation changes. If not, no action needed; if yes, trigger a manual canary before merge.

`redteam` / `kimi-k2.6:cloud`

Status: ok
Verdict: OK
Findings: none

Policy notes

GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
Auto-merge is not enabled here.

# Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `778` - Commit: `1d2d1921c83c2cdb1c14dda26cb7f0c6c0b5d48d` - Security-sensitive label: `missing` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings No deterministic findings. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `OK` - **`low`** Missing canary for docs-only PR - Evidence: `PR description states 'Canary status: missing - fire canary manually if required by repo policy'. The PR is documentation-only, but if the repository enforces canary for all merges, this may be a process gap.` - Next: Confirm whether the repo policy requires a canary for documentation changes. If not, no action needed; if yes, trigger a manual canary before merge. ### `redteam` / `kimi-k2.6:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.

patchwarden commented

2026-06-10 23:09:24 +02:00

First-time contributor

No Patchwarden findings to render.

patchwarden commented

2026-06-10 23:13:06 +02:00

First-time contributor

No Patchwarden findings to render.

patchwarden commented

2026-06-10 23:16:23 +02:00

First-time contributor

No Patchwarden findings to render.

patchwarden commented

2026-06-10 23:18:55 +02:00

First-time contributor

No Patchwarden findings to render.

codex added the

labels

2026-06-11 08:15:20 +02:00

patchwarden commented

2026-06-11 11:21:21 +02:00

First-time contributor

No Patchwarden findings to render.

patchwarden commented

2026-06-11 11:23:11 +02:00

First-time contributor

No Patchwarden findings to render.

patchwarden commented

2026-06-11 11:24:32 +02:00

First-time contributor

No Patchwarden findings to render.

patchwarden commented

2026-06-11 11:26:44 +02:00

First-time contributor

No Patchwarden findings to render.

patchwarden commented

2026-06-11 11:28:18 +02:00

First-time contributor

No Patchwarden findings to render.

codex commented

2026-06-17 23:02:22 +02:00

Author

Collaborator

Role: executor

PR-zero verification before merge:

Reviewed diff: records runtime host-ops env cleanup; no containers restarted/recreated by this PR.
Values recorded are non-secret paths/image refs and rollback path.
git diff --check origin/main...HEAD -> clean.
Secret-pattern rg over touched report files -> no matches.

Merging as historical runtime evidence so the stale Honcho follow-up stops staying open as active queue noise.

**Role:** executor PR-zero verification before merge: - Reviewed diff: records runtime host-ops env cleanup; no containers restarted/recreated by this PR. - Values recorded are non-secret paths/image refs and rollback path. - `git diff --check origin/main...HEAD` -> clean. - Secret-pattern `rg` over touched report files -> no matches. Merging as historical runtime evidence so the stale Honcho follow-up stops staying open as active queue noise.