docs(questions): replace prior answers section with targeted Explainers responding to back-questions

collab/questions/00-bootstrap.md

@@ -200,30 +200,19 @@ project.md wouldn't be in this repo (or is that a blank placeholder file (or may
 6. Format/tooling: choose YAML + `yq` as the single supported format/tool. Approve?
 Yes
 
-## Answers/Explainers 2025-17-09-14:46
+## Explainers 2025-17-09-14:52
 
-- Name & install:
+- Subcommands vs flags-only (tradeoffs):
-  - Use `CodexHelper` as the entrypoint script. No system install; user adds repo script to PATH. Provide optional `bin/install.sh` to symlink into `~/bin`.
+  - Subcommands: clearer discoverability (`CodexHelper new-project|new-mode|run`), better `--help` per action, easier future growth. Flags-only keeps one surface but is harder to parse and extend. Recommend subcommands; flag-only aliases can follow later if wanted.
-- Binary discovery:
+- Project scaffolding examples:
-  - Resolve with `which codex` then `which codex-cli`; allow `CODEX_BIN` to override. If missing, print guidance; no auto-install.
+  - In project: `prompts/project.md` (narrative), optional `prompts/style.md` (coding/style), `codex.yaml` (mode/config/MCP placeholders), `codex.sh` (entrypoint). `runs/` created on first run and ignored by VCS.
-- CLI UX:
+  - `codex.sh` composes prompts: global system → mode rules → project narrative; passes them to `codex` with settings.
-  - Subcommands provide clearer UX and self-documentation; we recommend: `CodexHelper new-project`, `CodexHelper new-mode`, `CodexHelper run`. We can later add flag-only aliases if desired.
+- Mode/system prompt copies:
-- Where to run:
+  - Copy global/mode prompts into `prompts/_mode/` in the project as read-only templates (annotated header). Project becomes self-contained; users may edit if desired.
-  - Outside this repo: support `new-project` and `run` for user projects. Inside this repo: only `new-mode` (to scaffold a mode via markdown intake).
+- Optional mode-specific system overlay:
-- Project scaffolding contents:
+  - For modes that need extra or tweaked system-level rules, include `modes/<name>/system.md` merged before mode rules.
-  - Generate in project: `prompts/project.md` (narrative), optional `prompts/style.md` (coding/style notes), `codex.yaml` (mode/config/MCP placeholders), `codex.sh` (entrypoint wrapper). Create `runs/` on first run and add to `.gitignore`.
+- `project.md` here vs user projects:
-  - Copy mode/system prompts into project under `prompts/_mode/` as read-only copies (cannot enforce, but mark with header comment). `codex.sh` will compose prompts in order.
+  - This repo keeps a template (e.g., `templates/project/<mode>/prompts/project.md`) which bootstrap copies to user projects; users then author real content there.
-- Prompt composition:
-  - Stack: Global system rules → Mode rules → Project narrative. The optional mode-specific system overlay is an extra system-level rules file for a mode when it needs to extend or tweak the global system rules.
-  - Locations: `prompts/global/system.md` (repo-wide), `modes/<name>/system.md` (optional overlay), `modes/<name>/mode.md` (mode rules), project `prompts/project.md`.
-- Config/tooling:
-  - Use YAML with `yq`. Precedence: CLI > env > project > mode > global defaults. Pass through sandbox/full-auto flags to codex.
-- Safety & outputs:
-  - Never overwrite without `--force`. Never run `git push` for user projects. Write runs to `<project>/runs/<timestamp>/...`. Prevent `run` inside this repo except for `new-mode`.
-- Licensing:
-  - Repo (wrapper, modes, prompts) under AGPLv3. User project artifacts (prompts/code generated) are user-licensed; we will not inject a LICENSE into projects.
-- OS target:
-  - Ubuntu 22.04/Debian 12+ with bash/zsh. Dependencies: bash, git, yq.
 
 7. Precedence final confirm: CLI > env > project > mode > global defaults. Approve?
 

devlog/DEVLOG_HUMAN.md

@@ -43,3 +43,13 @@ Summary:
 
 Next Steps:
 - Wait for your edits/approval in `collab/questions/00-bootstrap.md`.
+
+---
+
+Date: 2025-09-17 14:52 (UTC)
+
+Summary:
+- Adjusted questions doc to replace prior “Answers/Explainers” with an “Explainers” section focused on responding to your back-questions (subcommand tradeoffs, scaffolding examples, overlay purpose, project.md template behavior).
+
+Next Steps:
+- Await your confirmation or additional edits; then, on approval, I’ll draft the proposal and plan.

devlog/DEVLOG_LLM.md

@@ -34,3 +34,10 @@ This log is concise and structured for quick machine parsing and summarization.
   - Proposals/plans only after questions approved
 - next:
   - Wait for questions file edits/approval
+
+## 2025-09-17T14:52Z
+- context: Clarified intent for explainers vs user answers
+- actions:
+  - Replaced prior “Answers/Explainers” with targeted “Explainers” answering back-questions (subcommands tradeoffs, scaffolding examples, overlay purpose)
+- next:
+  - Await further inline edits or approval to proceed to proposal/plan