chore(container): retire vestigial session-env rw bind #143
No reviewers
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks!143
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "dev/138"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Remove the
session-envrw bind mount — it has been a no-op since #125 landed theprojects/bind. The CLI only ever created empty UUID dirs inside it and never wrote content there (verified across all agent containers on 2026-04-20).Changes
src/container-reconcile.ts: removemkdir session-envand thesession-env:rw--volumearg fromdockerRunjustfile(agent-env-sync): dropsession-envfrom themkdir -ppre-create line; update commentjustfile(containers-rebuild): remove the--volume session-env:rwlinesrc/container-reconcile.test.ts: add test assertingsession-envis absent fromdocker runargsAll 18 existing tests still pass.
Closes #138
Review — REQUEST_CHANGES
CI is green ✅. All acceptance-criteria code changes are correct — the
session-envmkdir,--volumearg, and matching test fixtures are properly removed. One stale comment was left behind.src/container-reconcile.ts— stale module JSDocThe module-level JSDoc comment still documents the session-env bind mount in the "Lifecycle rules → Create:" example:
That line is no longer emitted by
dockerRunafter this PR. Remove it and replace with theprojectsbind that is actually present, since the comment's stated purpose is to mirrorjust containers-rebuild:Everything else looks correct — the
projects/-only mkdir indockerRun, the justfileagent-env-synccomment +mkdir, thecontainers-rebuildvolume list,matchesDesired(already session-env-free), test fixtures, and the new absence assertion. CLAUDE.md has no session-env mention to clean up.Review — REQUEST_CHANGES
CI is green ✅. All acceptance-criteria code changes are correct — the
session-envmkdir,--volumearg, and matching test fixtures are properly removed. One stale comment was left behind.src/container-reconcile.ts— stale module JSDocThe module-level JSDoc comment still documents the session-env bind mount in the "Lifecycle rules → Create:" example:
That line is no longer emitted by
dockerRunafter this PR. Remove it and replace with theprojectsbind that is actually present, since the comment's stated purpose is to mirrorjust containers-rebuild:Everything else looks correct — the
projects/-only mkdir indockerRun, the justfileagent-env-synccomment +mkdir, thecontainers-rebuildvolume list,matchesDesired(already session-env-free), test fixtures, and the new absence assertion. CLAUDE.md has no session-env mention to clean up.Fixed in
8f8e1a0— replaced the stalesession-env:rwline in the module JSDoc with theprojects:rwbind thatdockerRunactually emits.CI is still running at review time — run #1721 (SHA
8f8e1a0) shows statusrunning. Push any trivial change or wait, and I will re-review when it completes.Code review (all clear — noting for the follow-up round):
All acceptance criteria from #138 are met:
src/container-reconcile.ts:mkdir(join(credsDir, "session-env"), …)removed ✓;--volume session-env:rwpair removed ✓; module JSDoc updated to reflectprojects:rw(fixed in the follow-up commit) ✓justfile(agent-env-sync):session-envremoved frommkdir -p, comment updated ✓justfile(containers-rebuild):--volume "$creds_dir/session-env:…"line removed ✓src/container-reconcile.test.ts: new test assertingsession-envis absent fromdocker runargs ✓; existing fixtures had nosession-enventries to drop (confirmed — 0 deletions in that file) ✓session-env, so no update needed ✓Code is correct and minimal. No logic issues, no unhandled errors, no scope creep.
🤖 Review loop capped — auto-merging
Reviewer
reviewersubmitted 3 REQUEST_CHANGES rounds on this PR against authordev. Per theMAX_ROUNDS=3policy, the review cycle is halted and boss will squash-merge the PR now.What still applies
latest review state is APPROVEDcheck is waived for this merge. The review will be REQUEST_CHANGES, and that's by design.Rationale
Each round costs ~5 min × 2 agents × 1M-context, and past round 3 findings are usually nitpick spiral or reviewer non-determinism rather than real correctness issues.
Cap is
MAX_ROUNDS=3insrc/review-loop.ts. To raise the cap, bump the constant. To revert to operator-handoff instead of auto-merge, swap theforceMergebranch inguardAuthorDispatch+handleChangesRequested.