[makeitworkbot]

Summary

Select published opencode-server:0.5.6, retaining application 2.0.22, API selector 2, and codebase-memory backend 0.10.8. The chart changes consumer instructions only; backend migration is not authorized.

Generated by charts publication, then manually coordinated: the Application pin and exact CI chart assertion must advance together in this PR. No assertion-only merge or check bypass.

Producer: charts #131, merge 09a08579; publication CI passed, including Publish chart and GitOps updater.

Type of change

• GitOps desired state
• CI / validation: update the coupled expected chart version only

Validation

• Fresh cluster checks passed on corrected HEAD afa27a0 (CI); main CI and automatic root-sync submission also passed. The original pin-only failure is not acceptance evidence.
• Producer chart tests, package, publication, and independent reviews passed.
• No hand-edited generated copies; only the Application chart selection and its exact CI assertion are coordinated.

Impact and rollout

Owner confirmed proceeding with chart publication and its documented automatic pin delivery. Existing auto-merge is enabled and can merge after required checks pass; there is no independent human deployment gate. The subsequent successful main test triggers root-sync requests at its tested Git SHA. Submission does not establish root/child reconciliation, pod readiness, or functional behavior; verify each separately.

Expected delta: desired pin and assertion 0.5.5 -> 0.5.6; API selector remains 2; agent-pipe chart remains 0.2.0. No change to backend, tool filters, resources, images, credentials, persistent data, or workflow jobs/permissions. Existing App-of-Apps, operator/CRD gates, and sync-wave boundaries remain.

After rollout verify root and OpenCode child revisions/sync/health, resource tree, replacement pod/image, delivered policy, and a fresh-session legacy-schema source read. Candidate backend resource/recovery/schema acceptance remains separately held. Rollback requires a separately approved PR selecting the previous immutable chart and matching assertion; do not revert compatibility while a later candidate backend depends on it.

Safety and secrets

• No secret material, state, kubeconfigs, sensitive plans, or decrypted values retrieved or changed.
• No local OpenTofu or live patch/sync/restart/exec operations performed.
• CI, publication, selection, reconciliation, readiness, and function are distinct evidence stages.

AI-assisted manual coordination by the Make IT Work Cloud agent; initial pin generated by the charts post-publish workflow.

[xnoto]

Coordinated the exact expected chart assertion with the generated pin in this same PR: both now select 0.5.6; API selector remains 2. Correction commit afa27a0. Adversarial, infrastructure-security, and delivery-integration reviews advanced the complete two-line delta without Critical/High findings before submission. No checks were bypassed. Fresh CI on this corrected HEAD must pass before existing auto-merge proceeds. Backend remains 0.10.8; this is not a backend migration.

[xnoto]

Bounded rollout verification — 2026-10-26

• Published: charts #131 merge 09a08579; producer main CI succeeded including OCI publication.
• Validated and selected: corrected PR HEAD afa27a0 CI completed successfully, including the CI-logging job. Existing auto-merge selected both pin and assertion atomically as 00469e89a658ffab0659d732920b792674d18ecd. Main CI and automatic root-sync submission succeeded.
• Reconciled / healthy: gitops-workloads Synced/Healthy at 00469e89; opencode Synced/Healthy at chart 0.5.6, uploader 0.2.0, and cluster revision 00469e89; successful operations, no unhealthy resource-tree entries.
• Ready / delivered: Deployment generation 44 observed, 1/1 updated/ready/available; replacement Pod opencode-5b7857986f-lhvqt Running/Ready with zero restarts. Deployment retains the pinned OpenCode 2.0.22 image. Live ConfigMap contains schema-aware floor/primary and strict full-source/fallback markers; the server-local shared instructions also contain the new routing contract.
• Representative function: a fresh Luna worker completed legacy advertised-schema status -> exact Module -> full snippet -> stable-root recheck for published Chart.yaml, returning complete lines 1–7, chart 0.5.6 / app 2.0.22, without clipping. The first attempt missed the project on the first discovery page; parent verified its presence and the worker completed after correction. Primary independently confirmed the full legacy snippet and stable verified root. This is not first-attempt or exhaustive agent-adherence proof.
• Unchanged backend: live MCPServer remains codebase-memory-mcp@0.10.8, --ui=false, Ready.

No manual sync, restart, exec, patch, workflow dispatch, or backend mutation was performed. Candidate 0.12.1 native/schema boundary, cold-start, resource, artifact, symlink and recovery acceptance remain unverified and separately held; this rollout does not authorize backend upgrade. Authenticated end-user OpenCode HTTP/UI behavior and exhaustive agent behavior were not tested.