cc-ci/machine-docs/JOURNAL-cfold.md

JOURNAL — phase cfold (Builder)

Design rationale, investigations, and dead-ends. Adversary does NOT read this before forming its verdict (anti-anchoring per plan §6.1). See STATUS-cfold.md for claim context.

---

2026-06-12 — bootstrap + initial orient

Read in full:

• /srv/cc-ci/cc-ci-plan/plan-phase-cfold-custom-folder.md
• /srv/cc-ci/cc-ci-plan/plan.md bootstrap plus §§6.1, 7, 9

Initial repo/phase state after git pull --rebase:

• pulled Adversary updates 574306e -> 87566b1
• machine-docs/BACKLOG-cfold.md and machine-docs/REVIEW-cfold.md existed already
• machine-docs/STATUS-cfold.md and machine-docs/JOURNAL-cfold.md were missing

Bootstrap checks run from this clone:

ssh cc-ci 'hostname && whoami && nixos-version'
# nixos
# root
# 24.11.20250630.50ab793 (Vicuna)

set -a && . /srv/cc-ci/.testenv && set +a && curl -s "https://$GITEA_URL/api/v1/version"
# {"version":"1.24.2"}

getent hosts "probe-$RANDOM.ci.commoninternet.net"
# 91.98.47.73 probe-22588.ci.commoninternet.net

Initial cfold code scan confirms the planned touch points are still unmigrated:

• runner/harness/discovery.py still globs ("functional", "playwright")
• runner/harness/manifest.py still reports subdir names verbatim
• unit tests still build fixtures under functional/ and playwright/
• repo grep still finds many folder-name references in docs/tests and the recipe trees themselves

Adversary inbox/review updates at 2026-06-12T00:00Z and 2026-06-12T16:00Z were procedural only: no claim pending, phase status file missing on origin/main. Consuming machine-docs/BUILDER-INBOX.md in the same commit that seeds cfold state.

Next: implement the smallest M1 slice first: discovery + alias policy + unit/manifest updates, then migrate the recipe trees and docs, then assemble the before/after coverage proof.