fix(vault): remove safe-session runtime dependency #619

Merged

pdurlej merged 1 commit from codex/m04-safe-session-vault-dependency-cleanup into main 2026-05-30 02:33:56 +02:00

Conversation 2 Commits 1 Files changed 8 +188 -26

codex commented 2026-05-30 01:24:01 +02:00

Collaborator

Copy link

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

Summary

Removes safe-session-api as a live HashiCorp Vault runtime dependency after the approved M04 local OpenSSH CA cutover.

What changed

• Makes local-openssh-ca the default safe-session signer mode.
• Removes Vault env/mount/depends_on from the normal safe-session-api compose path.
• Adds compose/overlays/safe-session-vault-signer.yaml as the explicit rollback path.
• Tightens vault-sunset-readiness.sh so active HashiCorp Vault dependency env names fail, while unrelated VAULT_* names are reported as inventory.
• Documents that post-M01/M04 DR refresh must happen before destructive Vault cleanup.
• Adds tests for readiness pass/fail classification.

Runtime evidence

• M04-B runtime cutover was operator-approved with m04-vault-runtime-cutover-approved.
• Rebuilt and recreated only home-platform-safe-session-api-1 with the local CA overlay.
• safe-session-api: running/healthy.
• Vault: still running/healthy as rollback material.
• Local signer smoke: pass for llmops, denied root.
• SSH login smoke with issued cert: pass for llmops.
• Vault sunset readiness: pass.
• Readiness inventory still reports old home-platform-np-1 names: VAULT_BOOTSTRAP_EXAMPLES, VAULT_ROOT, VAULT_TIMEZONE; these are not classified as HashiCorp Vault dependency env names.

Validation

• pytest -q tests/test_vault_sunset_readiness.py tests/test_safe_session_ca_bootstrap.py scripts/safe-session-api/tests/test_local_signer.py -> 12 passed.
• PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json -> exitCode 0.
• RS2000 rollback overlay config: pass.

Non-goals

• Does not stop Vault.
• Does not delete Vault data, snapshots, env files, image, container, or CA material.
• Does not run quarantine.
• Does not run destructive cleanup.
• Does not replace the required post-M01/M04 DR refresh gate.

Spec sources read

• compose/core/compose.yaml
• compose/overlays/safe-session-local-ca.yaml
• scripts/safe-session-api/Dockerfile
• scripts/safe-session-api/server.py
• scripts/cutover/vault-sunset-readiness.sh
• runbooks/safe-session-local-ca-cutover.md
• runbooks/vault-quarantine-and-sunset.md

Requested decision

Review/merge as the M04-C cleanup PR. Next runtime gate is quarantine only after explicit m04-vault-quarantine-approved; destructive cleanup remains blocked until post-M01/M04 DR refresh and explicit destructive approval.

Canary status: missing — fire canary 3+3 manually before merge ## Summary Removes `safe-session-api` as a live HashiCorp Vault runtime dependency after the approved M04 local OpenSSH CA cutover. ## What changed - Makes `local-openssh-ca` the default safe-session signer mode. - Removes Vault env/mount/depends_on from the normal `safe-session-api` compose path. - Adds `compose/overlays/safe-session-vault-signer.yaml` as the explicit rollback path. - Tightens `vault-sunset-readiness.sh` so active HashiCorp Vault dependency env names fail, while unrelated `VAULT_*` names are reported as inventory. - Documents that post-M01/M04 DR refresh must happen before destructive Vault cleanup. - Adds tests for readiness pass/fail classification. ## Runtime evidence - M04-B runtime cutover was operator-approved with `m04-vault-runtime-cutover-approved`. - Rebuilt and recreated only `home-platform-safe-session-api-1` with the local CA overlay. - `safe-session-api`: running/healthy. - `Vault`: still running/healthy as rollback material. - Local signer smoke: pass for `llmops`, denied `root`. - SSH login smoke with issued cert: pass for `llmops`. - Vault sunset readiness: pass. - Readiness inventory still reports old `home-platform-np-1` names: `VAULT_BOOTSTRAP_EXAMPLES`, `VAULT_ROOT`, `VAULT_TIMEZONE`; these are not classified as HashiCorp Vault dependency env names. ## Validation - `pytest -q tests/test_vault_sunset_readiness.py tests/test_safe_session_ca_bootstrap.py scripts/safe-session-api/tests/test_local_signer.py` -> 12 passed. - `PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json` -> exitCode 0. - RS2000 rollback overlay config: pass. ## Non-goals - Does not stop Vault. - Does not delete Vault data, snapshots, env files, image, container, or CA material. - Does not run quarantine. - Does not run destructive cleanup. - Does not replace the required post-M01/M04 DR refresh gate. ## Spec sources read - `compose/core/compose.yaml` - `compose/overlays/safe-session-local-ca.yaml` - `scripts/safe-session-api/Dockerfile` - `scripts/safe-session-api/server.py` - `scripts/cutover/vault-sunset-readiness.sh` - `runbooks/safe-session-local-ca-cutover.md` - `runbooks/vault-quarantine-and-sunset.md` ## Requested decision Review/merge as the M04-C cleanup PR. Next runtime gate is quarantine only after explicit `m04-vault-quarantine-approved`; destructive cleanup remains blocked until post-M01/M04 DR refresh and explicit destructive approval.

codex added 1 commit 2026-05-30 01:24:01 +02:00

fix(vault): remove safe-session runtime dependency ... 75819b0e80

Make local OpenSSH CA the safe-session default after M04 cutover, move the Vault signer path into an explicit rollback overlay, and tighten Vault sunset readiness around actual HashiCorp Vault dependency env names.\n\nReadiness now reports unrelated VAULT_* names as inventory while failing on active Vault dependency variables. The quarantine runbook also records that post-M01/M04 DR refresh must precede destructive Vault cleanup.

codex commented 2026-05-30 01:31:12 +02:00

Author

Collaborator

Copy link

Patchwarden PR sanity

• Status: eligible_sanity_clean
• PR: 619
• Commit: fc45324172f3cae860c76f7f998351bc159e3673
• Security-sensitive label: present
• 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: error
• Verdict: -
• Note: ReadTimeout: The read operation timed out
• Findings: none

global-deepseek / deepseek-v4-pro:cloud

• Status: ok

• Verdict: OK

• low Readiness script may miss future Vault dependency env names

  • Evidence: scripts/cutover/vault-sunset-readiness.sh: is_hashicorp_vault_env_name() lists a fixed set of known HashiCorp Vault env names. If a new dependency uses an unlisted name (e.g., a custom or future Vault env var), it would be classified as inv
  • Next: Document the list as exhaustive for the current Vault integration and add a periodic review step in the runbook to update the list if Vault usage evolves.

redteam / kimi-k2.6:cloud

• Status: error
• Verdict: -
• Note: ReadTimeout: The read operation timed out
• 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:pdurlej/platform:PR-619 --> # Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `619` - Commit: `fc45324172f3cae860c76f7f998351bc159e3673` - Security-sensitive label: `present` - 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: `error` - Verdict: `-` - Note: ReadTimeout: The read operation timed out - Findings: none ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `OK` - **`low`** Readiness script may miss future Vault dependency env names - Evidence: `scripts/cutover/vault-sunset-readiness.sh: is_hashicorp_vault_env_name() lists a fixed set of known HashiCorp Vault env names. If a new dependency uses an unlisted name (e.g., a custom or future Vault env var), it would be classified as inv` - Next: Document the list as exhaustive for the current Vault integration and add a periodic review step in the runbook to update the list if Vault usage evolves. ### `redteam` / `kimi-k2.6:cloud` - Status: `error` - Verdict: `-` - Note: ReadTimeout: The read operation timed out - 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.

codex referenced this pull request 2026-05-30 01:38:34 +02:00

fix(ci): scope Patchwarden sanity artifacts per PR #621

codex force-pushed codex/m04-safe-session-vault-dependency-cleanup from 75819b0e80 to fc45324172 2026-05-30 02:11:38 +02:00 Compare

codex added the

class/security-sensitive

label 2026-05-30 02:13:02 +02:00

pdurlej approved these changes 2026-05-30 02:33:38 +02:00

pdurlej left a comment

Copy link

Operator-delegated approval via temporary admin PAT. Checks are green after rebase; DeepSeek V4 Pro red-team was GO; runtime cutover was already smoked on RS2000; this PR removes safe-session's Vault runtime dependency and does not quarantine or destroy Vault.

Operator-delegated approval via temporary admin PAT. Checks are green after rebase; DeepSeek V4 Pro red-team was GO; runtime cutover was already smoked on RS2000; this PR removes safe-session's Vault runtime dependency and does not quarantine or destroy Vault.

pdurlej merged commit a0657e1bc9 into main 2026-05-30 02:33:56 +02:00

pdurlej referenced this pull request from a commit 2026-05-30 02:33:57 +02:00

fix(vault): remove safe-session runtime dependency

codex referenced this pull request 2026-05-30 03:13:54 +02:00

docs(migrations): vault-to-infisical Phase 1-5 execution #64

codex referenced this pull request 2026-05-30 03:15:54 +02:00

test(dr): refresh post-M04 restore evidence before Vault quarantine #623

Sign in to join this conversation.

Reviewers

No reviewers

pdurlej

Labels

Clear labels   

W6d-automerge-calibration

  

agent/claude-code

Vistula actor: Claude Code.

  

agent/codex

Vistula actor: Codex.

  

agent/hermes

Vistula actor: Hermes Upstream.

  

agent/iskra

Vistula actor: Iskra.

  

agent/ollama

Vistula actor: Ollama or compatible model.

  

agent/patchwarden

Vistula actor: Patchwarden.

  

automerge-candidate

Candidate for narrow W6d autonomous merge readiness pilot

  

class/security-sensitive

Security-sensitive class of service: smallest coherent PRs and full canary

  

cutover-gate

blocks production declare / final RS2000 replacement

  

dependency/blocked

Vistula dependency state: blocked.

  

dependency/blocks-others

Vistula dependency state: blocks other work.

  

dependency/cross-repo

Vistula dependency scope: cross-repository.

  

dependency/needs-confirmation

Vistula dependency state: needs confirmation.

  

domain:agents

Agent identity, delegation, subagents, routing, or workflows.

  

domain:ci

CI, checks, Actions, runners, or release automation.

  

domain:docs

Documentation, packets, practices, or source-of-truth text.

  

domain:forgejo

Forgejo issues, PRs, labels, repo settings, or identity.

  

domain:infra

Infrastructure, storage, backup, DNS, network, or host substrate.

  

domain:memory

Memory, recall, write gates, salience, or Honcho-adjacent behavior.

  

domain:runtime

Runtime services, deploys, daemons, timers, or live behavior.

  

domain:signal

Signal UX, delivery, context, or outbound behavior.

  

domain:ux

Product UX, operator experience, or conversation ergonomics.

  

flow/architecture

Vistula lifecycle: architecture phase in progress.

  

flow/blocked

Vistula lifecycle: blocked on dependency or decision.

  

flow/deployed

Vistula lifecycle: deployed to runtime where applicable.

  

flow/done

Vistula lifecycle: work merged or otherwise done.

  

flow/implementation

Vistula lifecycle: implementation phase in progress.

  

flow/intake

Vistula lifecycle: incoming signal not refined yet.

  

flow/maintained

Vistula lifecycle: maintained/steady state.

  

flow/observed

Vistula lifecycle: observed after delivery.

  

flow/ready

Vistula lifecycle: ready for architecture or implementation.

  

flow/refining

Vistula lifecycle: Hermes/spec refinement in progress.

  

flow/retired

Vistula lifecycle: retired or intentionally closed.

  

flow/review

Vistula lifecycle: review phase in progress.

  

iterating

Orchestrator/Codex actively amending in response to review — operator can ignore until resolved

  

judge/codex-candidate

Candidate for Codex implementation.

  

judge/hermes-candidate

Candidate for Hermes discovery/research.

  

judge/low-confidence

Judgment confidence is low.

  

judge/needs-refinement

Needs clearer evidence or scope.

  

judge/operator-needed

Needs Piotr decision or input.

  

judge/p0

Urgent, operator attention or unblock now.

  

judge/p1

High value, schedule soon.

  

judge/p2

Useful, normal queue.

  

judge/p3

Low priority, keep but do not chase.

  

judge/park

Parked from current attention.

  

judge/patchwarden-candidate

Needs Patchwarden merge-safety attention.

  

judge/stale-priority

Existing priority judgment appears stale.

  

kind/adr

Vistula work kind: architecture decision record.

  

kind/bug

Vistula work kind: bug fix.

  

kind/chore

Vistula work kind: chore.

  

kind/feature

Vistula work kind: feature.

  

kind/infra

Vistula work kind: infrastructure.

  

kind/ops

Vistula work kind: operations.

  

kind/refactor

Vistula work kind: refactor.

  

kind/research

Vistula work kind: research/discovery.

  

large-impact

Per charter §3 review-by-impact: large impact (≥300 LOC OR new module OR identity/secret change OR architectural pivot) — Oracle pre-review recommended

  

merge/auto

Vistula merge mode: automated merge.

  

merge/manual

Vistula merge mode: manual merge.

  

merge/manual-dependency-conflict

Manual merge reason: dependency conflict.

  

merge/manual-failing-tests

Manual merge reason: failing tests.

  

merge/manual-merge-conflict

Manual merge reason: merge conflict.

  

merge/manual-missing-review

Manual merge reason: missing review.

  

merge/manual-operator-preference

Manual merge reason: operator preference.

  

merge/manual-red-zone

Manual merge reason: red-zone risk.

  

merge/manual-security-sensitive

Manual merge reason: security-sensitive work.

  

merge/manual-unclear-scope

Manual merge reason: unclear scope.

  

merge/manual-unknown

Manual merge reason: unknown.

  

meta

meta-decomposition issue; first agent decomposes into atomic children

  

mode:operator-only

Apply step requires explicit operator approval.

  

mode:patchwarden-iskra-approved

Work eligible for Patchwarden/Iskra approval inside repo policy.

  

mode:safe-auto

Low-risk work eligible for lightweight autonomous handling.

  

needs-operator-decision

PR is blocked on operator yes/no decision — fresh-Claude/Codex won't make this call alone

  

needs-triage

decomposing agent has open questions / unknowns

  

not-ready

reviewed but blocked on a precondition

  

observed/erroring

Vistula observation: erroring.

  

observed/needs-followup

Vistula observation: needs follow-up.

  

observed/pending

Vistula observation: pending.

  

observed/retire-candidate

Vistula observation: retire candidate.

  

observed/unused

Vistula observation: unused.

  

observed/used

Vistula observation: used.

  

operator-emotional

operator-emotional importance (Iskra memory etc.)

  

owner-attention

owner must decide; blocks default path

  

phase/02

Phase 02 cataloging

  

phase/03

Phase 03 control plane (platformctl)

  

priority:p0

Immediate safety, uptime, data, or operator-blocking issue.

  

priority:p1

Important active work; should be pulled soon.

  

priority:p2

Useful normal-priority work.

  

priority:p3

Opportunistic cleanup, research, or backlog work.

  

proposed

auto-generated by meta-decomposition; awaiting human review

  

ready-for-agent

reviewed and pickable; agents may claim per cookbook

  

ready-for-operator

PR is ready for operator review/merge — orchestrator finished its part

  

recovery

disaster recovery / restore semantics relevant

  

review:claude-reviewed

Reviewed by Claude-family agent.

  

review:codex-reviewed

Reviewed by Codex-family agent.

  

review:dziadek-reviewed

Reviewed by Dziadek pinch-point reviewer.

  

review:needs-human

Needs human review before merge or apply.

  

risk/exposure

incorrectly public/private/tailnet/auth/routed

  

risk/process

workflow/review/orchestration may produce bad outcomes

  

risk/product

work may have lost owner/user value

  

risk/runtime

platform may not run, recover, validate, behave reproducibly

  

safety:external-write

May write to external systems, users, rooms, repos, or services.

  

safety:no-prod-mutation

Must not mutate production or live external state.

  

safety:prod-impact

May affect production/runtime behavior.

  

safety:secret-touch

Touches secrets, credentials, auth, or secret-adjacent config.

  

size/large

Vistula size: large.

  

size/medium

Vistula size: medium.

  

size/small

Vistula size: small.

  

size/tiny

Vistula size: tiny.

  

size/unknown

Vistula size: not classified yet.

  

source/adr

Vistula source: ADR.

  

source/agent-generated

Vistula source: agent generated.

  

source/manual

Vistula source: manual entry.

  

source/operator-chat

Vistula source: operator chat.

  

source/voice-note

Vistula source: voice note.

  

status:blocked

Blocked by missing dependency, evidence, access, or operator decision.

  

status:codex-ready

Ready for a Codex implementation pass.

  

status:merged:pending-evidence

Merged but waiting for live or artifact evidence before closure.

  

status:needs-evidence

Needs proof, logs, tests, or operator-visible evidence.

  

status:operator-needed

Requires explicit operator input before safe progress.

  

status:parked

Intentionally deferred; not active campaign work.

  

tier/full

Full review tier per ADR-0007

  

tier/lite

Lite review tier per ADR-0007

  

tier/stacked

Stacked PR (base != main) escape hatch per ADR-0017. Requires consolidator-PR plan in PR body.

  

tier:0-platform-substrate

Data, secrets, backup, storage, or critical platform substrate.

  

tier:1-iskra-value-layer

Iskra/OpenClaw behavior, memory, runtime, or value-layer work.

  

tier:2-tools-products-modules

Tools, products, modules, experiments, and lower-blast-radius work.

  

type:bug

Incorrect behavior or regression.

  

type:chore

Maintenance, cleanup, metadata, or operational task.

  

type:docs

Documentation-only work.

  

type:feat

New capability or product behavior.

  

type:policy

Governance, protocol, boundary, or decision-contract change.

  

type:research

Investigation, spike, or evidence-gathering task.

No labels

W6d-automerge-calibration

agent/claude-code

agent/codex

agent/hermes

agent/iskra

agent/ollama

agent/patchwarden

automerge-candidate

class/security-sensitive

cutover-gate

dependency/blocked

dependency/blocks-others

dependency/cross-repo

dependency/needs-confirmation

domain:agents

domain:ci

domain:docs

domain:forgejo

domain:infra

domain:memory

domain:runtime

domain:signal

domain:ux

flow/architecture

flow/blocked

flow/deployed

flow/done

flow/implementation

flow/intake

flow/maintained

flow/observed

flow/ready

flow/refining

flow/retired

flow/review

iterating

judge/codex-candidate

judge/hermes-candidate

judge/low-confidence

judge/needs-refinement

judge/operator-needed

judge/p0

judge/p1

judge/p2

judge/p3

judge/park

judge/patchwarden-candidate

judge/stale-priority

kind/adr

kind/bug

kind/chore

kind/feature

kind/infra

kind/ops

kind/refactor

kind/research

large-impact

merge/auto

merge/manual

merge/manual-dependency-conflict

merge/manual-failing-tests

merge/manual-merge-conflict

merge/manual-missing-review

merge/manual-operator-preference

merge/manual-red-zone

merge/manual-security-sensitive

merge/manual-unclear-scope

merge/manual-unknown

meta

mode:operator-only

mode:patchwarden-iskra-approved

mode:safe-auto

needs-operator-decision

needs-triage

not-ready

observed/erroring

observed/needs-followup

observed/pending

observed/retire-candidate

observed/unused

observed/used

operator-emotional

owner-attention

phase/02

phase/03

priority:p0

priority:p1

priority:p2

priority:p3

proposed

ready-for-agent

ready-for-operator

recovery

review:claude-reviewed

review:codex-reviewed

review:dziadek-reviewed

review:needs-human

risk/exposure

risk/process

risk/product

risk/runtime

safety:external-write

safety:no-prod-mutation

safety:prod-impact

safety:secret-touch

size/large

size/medium

size/small

size/tiny

size/unknown

source/adr

source/agent-generated

source/manual

source/operator-chat

source/voice-note

status:blocked

status:codex-ready

status:merged:pending-evidence

status:needs-evidence

status:operator-needed

status:parked

tier/full

tier/lite

tier/stacked

tier:0-platform-substrate

tier:1-iskra-value-layer

tier:2-tools-products-modules

type:bug

type:chore

type:docs

type:feat

type:policy

type:research

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

pdurlej/platform!619

No description provided.