Skip to content
This repository was archived by the owner on Aug 10, 2026. It is now read-only.

chore: untrack .blackwall/ custody store (no scrub) - #12

Merged
todie merged 3 commits into
mainfrom
chore/untrack-blackwall-store
Aug 9, 2026
Merged

chore: untrack .blackwall/ custody store (no scrub)#12
todie merged 3 commits into
mainfrom
chore/untrack-blackwall-store

Conversation

@todie

@todie todie commented Aug 8, 2026

Copy link
Copy Markdown
Member

What

Removes the .blackwall/ custody store (416 files, 2.6 MB) from the git index and adds it to .gitignore. Working copies stay on disk; history is retained — the operator ruling (2026-08-08) was explicit: untrack, no scrub.

Why

  • Blackwall doctrine: .blackwall/ — local custody store (gitignored; never committed) (blackwall CLAUDE.md), plus the estate-wide "gitignore .blackwall/" rollout (soma-os docs/soma/GROUND-TRUTH-2026-07-24.md). escapement was the straggler.
  • CER-1781 P2 (escapement→monorepo migration) would otherwise copy runtime custody state into the migration snapshot. Punch-list item 6, reverie #21063.

Verification

git rm -r --cached only — git status shows 416 D (index) + .gitignore M, zero working-tree deletions. Fresh clones stop receiving the store; existing checkouts keep their local state.

todie added 2 commits August 8, 2026 05:16
… no scrub)

The .blackwall/ custody store (416 files, 2.6 MB) was tracked in git,
contradicting blackwall doctrine ('.blackwall/ — local custody store
(gitignored; never committed)') and the estate-wide gitignore rollout
recorded in soma-os GROUND-TRUTH-2026-07-24. Index-only removal
(git rm --cached) — working copies stay on disk; history retained per
the explicit no-scrub ruling. Blocks CER-1781 P2 from copying custody
state into the monorepo snapshot.
The untrack commit staged only the git rm --cached deletions; the
.gitignore append was a working-tree edit never added, so the pushed PR
left .blackwall/ untracked-but-unignored — one 'git add -A' from being
re-committed. Caught by jury review.
@todie

todie commented Aug 8, 2026

Copy link
Copy Markdown
Member Author

Agent jury — ✅ approved (high confidence, after 1 blocker fixed)

Session-jury verdict (adversarial reviewer, read-only; distinct from the workflow checks).

Blocker caught + fixed: the original commit staged only the git rm --cached deletions — the .gitignore entry was a working-tree edit never added, so the PR as first pushed left .blackwall/ untracked-but-unignored, one git add -A from silent re-tracking. Fixed in 14ff256; git check-ignore -v confirms the rule is live against the committed HEAD.

Verified clean: exactly 416 D (all .blackwall/) + 1 M (.gitignore), nothing else; content adjudicated as blackwall's internal audit-trail git repo (runtime state, not source/config); secret scan of retained history: zero matches (no-scrub ruling stands well-informed); no code/CI reads a tracked .blackwall path (2 prose mentions only); working tree untouched (index-only, per ruling).

Merge on green per operator authorization (2026-08-08).

@todie todie closed this Aug 9, 2026
@todie todie reopened this Aug 9, 2026
…ale-set labels

The public-repo-ci group serves ci-rust/reverie-ug scale sets; ARC runners
carry only their scale-set name as label, so runs-on: self-hosted queued
forever after the repo went public (same label-mismatch class as OPS-1140).
The edge typecheck needs no cluster access — GitHub-hosted is correct.
@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown

🤖 Agent Jury — Review Failed

The GLM-5.2 review could not complete (gateway error or invalid response).
Manual review required.

Field Value
Model glm-5.2
Status ⚠️ failed

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown

🤖 Agent Jury — Review Failed

The GLM-5.2 review could not complete (gateway error or invalid response).
Manual review required.

Field Value
Model glm-5.2
Status ⚠️ failed

@todie
todie merged commit c93b3db into main Aug 9, 2026
4 of 5 checks passed
@todie
todie deleted the chore/untrack-blackwall-store branch August 9, 2026 20:56
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant