chore: add collab/ structure; move questions; add AGENTS.md; addendum in SeedPrompt.md

collab/00-bootstrap-plan.md

@@ -0,0 +1,11 @@
+# 00 — Bootstrap — Plan
+
+1. Create `collab/` directory for coordination artifacts.
+2. Move `QUESTIONS.md` to `collab/00-bootstrap-questions.md`.
+3. Add `collab/00-bootstrap-proposal.md` and this plan file.
+4. Create `AGENTS.md` capturing repository working agreements.
+5. Append Addendum to `SeedPrompt.md` describing the new structure.
+6. Commit and push changes to `main`.
+
+Status: pending review/confirmation.
+

collab/00-bootstrap-proposal.md

@@ -0,0 +1,20 @@
+# 00 — Bootstrap — Proposal
+
+Purpose: Formalize the collaboration scaffolding and initial workflow.
+
+Scope:
+- Use `collab/` directory to host questions, proposals, and plans.
+- Adopt filename pattern: `<step-or-subject>-<type>.md`, where `<type>` ∈ {`questions`, `proposal`, `plan`}.
+- Maintain `AGENTS.md` with working conventions and agent guidance.
+
+Deliverables (this step):
+- collab/00-bootstrap-questions.md (moved from root)
+- collab/00-bootstrap-proposal.md (this file)
+- collab/00-bootstrap-plan.md (skeleton)
+- AGENTS.md (initial content)
+- SeedPrompt.md updated with an Addendum describing this structure
+
+Acceptance Criteria:
+- Repo contains the above files with agreed naming scheme.
+- CI not required; manual review suffices for this step.
+

collab/00-bootstrap-questions.md

@@ -0,0 +1,31 @@
+# 00 — Bootstrap — Questions
+
+These questions guide the initial design and implementation. Please answer inline.
+
+## Repo & workflow
+1. Git remote: Should we push to an existing remote? If yes, provide the remote URL and branch (default `origin main`).
+2. Tagging: Use `YYYY-MM-DD-HHMM` in local time or UTC? Use `tea` only for tagging/releases, or also for pushes?
+3. Commit cadence: Any specific commit style (e.g., Conventional Commits)?
+
+## codex-cli wrapper
+4. codex-cli path: How is `codex`/`codex-cli` invoked in your environment (command name, install path)?
+5. Defaults: Preferred default model, token budget, and reasoning level?
+6. Config precedence: Order of overrides? (e.g., CLI flags > env vars > project config > mode config > global defaults)
+7. Config files: Desired locations/names? (e.g., `.codexrc`, `.codex/mode.yaml`, `project.yaml`)
+8. Prompts storage: Where to store Global System Prompt, Mode Prompt, and Project Prompt? (proposal: `modes/<name>/system.md`, `modes/<name>/mode.md`, `projects/<name>/prompt.md`)
+9. MCP configuration: Expected format and location? (JSON/YAML/TOML; per-mode vs per-project)
+
+## Wizards
+10. Mode wizard fields: Minimum fields for a mode (name, description, defaults, prompts, MCP config)? Any templates you prefer?
+11. Project wizard fields: Minimum fields for a project (name, path, project prompt, default mode, overrides)?
+
+## Execution behavior
+12. Mode selection: CLI flags `--mode`, `--project`, and optional `--prompt-file` acceptable?
+13. Non-interactive: Should wrapper fully resolve configs non-interactively by default, with an `--interactive` flag for wizard-like prompting?
+14. Output handling: Where to log transcripts or runs? (proposal: `runs/<timestamp>/…`)
+15. Safety: Any commands that must never be executed without confirmation?
+
+## Misc
+16. Licensing/headers: Any repo-specific requirements beyond the existing LICENSE?
+17. Supported OS/shells: Target bash/zsh on macOS/Linux, anything else?
+