status(1d): bootstrap Phase 1d — design recorded (tier model, override precedence, deploy-once), state files seeded

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

machine-docs/JOURNAL-1d.md

@@ -0,0 +1,29 @@
+# JOURNAL — Phase 1d (append-only)
+
+## 2026-05-27 — Bootstrap Phase 1d
+
+Read SSOT `plan-phase1d-generic-test-suite.md` + plan.md §6.1/§7/§9. Studied the post-1b codebase:
+`runner/run_recipe_ci.py` (per-stage pytest, currently deploy-per-stage), `tests/conftest.py`
+(fixtures `deployed_app`/`deployed`/`old_app` each deploy+teardown), `runner/harness/{lifecycle,abra,naming}.py`,
+and existing recipe tests (custom-html/keycloak/etc.).
+
+Access re-verified (bootstrap, new phase):
+```
+$ ssh cc-ci 'hostname && whoami && nixos-version'
+nixos / root / 24.11.20250630.50ab793 (Vicuna)
+$ ssh cc-ci 'abra --version'        -> abra version 0.13.0-beta-06a57de
+$ ssh cc-ci 'docker stack ls'       -> traefik, drone, ccci-bridge, ccci-dashboard, backups all up
+$ ssh cc-ci 'grep -ri backupbot ~/.abra/recipes/custom-html/'
+  compose.yml: backupbot.backup=true ; backupbot.backup.path=/usr/share/nginx/html
+$ curl -u bot ... /repos/recipe-maintainers/custom-html-tiny  -> 200 (mirrored)
+```
+So: backup-capability is detectable by scanning compose for `backupbot.backup`; custom-html-tiny is
+mirrored and has NO cc-ci tests dir → it's the DG1 pure-generic target.
+
+**Design recorded in DECISIONS.md (Phase 1d section).** Key calls: tier model with the lifecycle OP
+owned by the shared harness (test files = assertions only); OVERRIDE precedence repo-local > cc-ci >
+generic with extend-by-composition; deploy-ONCE with a deploy-count guard; base version = previous
+(when upgrade runs) else target; backup-capability auto-detect; install-steps shell hook.
+
+Seeded STATUS-1d / BACKLOG-1d / JOURNAL-1d. Next: implement G0 (generic.py + discovery.py +
+tests/_generic/ + deploy-once orchestrator), then verify generic install green on custom-html-tiny.