theslopmachine 1.0.3 → 1.0.5

package/MANUAL.md

@@ -39,7 +39,7 @@ Inside a new or empty project directory, run:
 slopmachine init
 ```
 
-Or to open OpenCode immediately in `repo/` after bootstrap:
+Or to open OpenCode immediately in `task/` after bootstrap:
 
 ```bash
 slopmachine init -o
@@ -47,32 +47,32 @@ slopmachine init -o
 
 ## What `init` does
 
-- creates `.ai/` workflow files plus `.ai/artifacts`
-- creates hidden `.ai/worktrees/` as the default location for parallel git worktrees
-- initializes git when needed
-- updates `.gitignore`
+- creates workflow-root `.ai/` workflow files plus `.ai/artifacts`
+- creates hidden workflow-root `.ai/worktrees/` as the default location for parallel git worktrees
+- creates `task/` and initializes git inside `task/`
+- updates `task/.gitignore`
 - bootstraps beads_rust (`br`)
-- creates parent-root `docs/`, `.tmp/`, `metadata.json`, and root `.beads/`
-- creates `repo/`
-- copies the packaged default repo rulebook into `repo/AGENTS.md`
-- copies the packaged Claude repo rulebook into `repo/CLAUDE.md`
-- seeds `repo/README.md`, `repo/plan.md`, and `repo/.claude/settings.json`
-- seeds `.ai/startup-context.md` plus the parent-root planning docs under `docs/`
-- later, when `P5` closes, the workflow preserves the final truthful execution record in `docs/plan.md` and removes `repo/plan.md` before evaluation begins
+- creates workflow-root `.beads/` outside `task/`
+- creates task-root `docs/`, `.tmp/`, `metadata.json`, and `repo/`
+- copies the packaged default rulebook into `task/AGENTS.md`
+- copies the packaged Claude rulebook into `task/CLAUDE.md`
+- seeds `task/repo/README.md`, task-visible product docs, and `task/.claude/settings.json`
+- seeds `.ai/startup-context.md` plus owner-private planning files under `.ai/`
+- keeps execution planning owner-private in `.ai/plan.md`
 - creates the initial git commit so the workspace starts with a clean tree
-- optionally opens `opencode` in `repo/`
-- parallel worktrees should stay under hidden parent-root `.ai/worktrees/` so the visible workspace root stays clean
+- optionally opens `opencode` in `task/`
+- parallel worktrees should stay under hidden workflow-root `.ai/worktrees/` so the visible task root stays clean
 
 ## Rough workflow
 
 1. Intake and setup
 2. Clarification
 3. Planning
-4. Development, starting with the scaffold step inside `plan.md`
+4. Development, starting with scaffold and then module-by-module owner prompts
 5. Rough integrated verification and hardening: repo coherence and small owner-side fixes only, with no Docker execution
 6. Evaluation and fix verification, including the final coverage and README audit inside `P7`
 7. Final readiness decision
-8. Submission packaging, including the owner-only Docker and `./run_tests.sh` check
+8. Submission packaging, including the owner-only Docker and `./repo/run_tests.sh` check
 9. Retrospective
 
 The intended fast path is:
@@ -82,7 +82,7 @@ The intended fast path is:
 - execute the plan end to end
 - make the repo coherent
 - proceed through evaluation without Docker execution
-- after evaluation is complete, have the owner run and fix `docker compose up --build` and `./run_tests.sh` before submission closes
+- after evaluation is complete, have the owner run and fix `docker compose up --build` and `./repo/run_tests.sh` before submission closes
 
 ## Important notes
 
@@ -92,5 +92,5 @@ The intended fast path is:
 - packaging and send-data depend on archive support: `zip` on non-Windows systems or PowerShell on Windows.
 - The workflow-owner agents use mandatory skills for specific phases; skipping them is considered a workflow failure.
 - `slopmachine` is the lighter current engine: it keeps the owner prompt smaller, uses more specialized skills, and keeps one active developer session at a time while preserving rollover history when new sessions are intentionally started.
-- the scaffold playbook inventory now covers the main repeated families used in current tasks: React/Vite, Vue/Vite, Angular, FastAPI, Spring Boot, Django, Laravel, Livewire, Go/Chi, Android Java Views, Android Kotlin Compose, Electron/Vite, Tauri, Expo iOS-on-Linux, plus honest Linux partial-proof native Swift and Objective-C iOS playbooks.
+- the scaffold playbook inventory covers current packaged type, technology, and composed-stack playbooks under `~/slopmachine/scaffold-playbooks/`; unsupported stacks fall back to the generic scaffold path instead of a nonexistent named playbook.
 - Submission packaging collects the final docs, accepted evaluation reports, cleaned OpenCode session exports or one Claude session zip bundle containing only the tracked relevant Claude sessions, and the cleaned repo into the required final structure.

package/README.md

@@ -85,29 +85,24 @@ Notes:
 
 Current scaffold inventory includes:
 
-- shared Docker/runtime/test contract
-- generic unknown-tech scaffold guide
-- frontend, backend, database, platform, and overlay family matrices
-- experimentally verified concrete playbooks for:
-  - React/Vite
-  - Vue/Vite
-  - Angular
-  - FastAPI
-  - Spring Boot
-  - Django
-  - Laravel
-  - Livewire
-  - Go/Chi
-  - Android Java Views
-  - Android Kotlin Compose
-  - Electron/Vite desktop
-  - Tauri desktop
-  - Expo iOS-on-Linux
-- experimentally verified Linux partial-proof playbooks for:
-  - native Swift iOS
-  - native Objective-C iOS
-
-These playbooks are baseline-only references. The redesigned workflow uses them to define the scaffold step at the start of development inside `plan.md` before the single broad implementation run continues.
+- shared runtime/test contract
+- stack selection matrix
+- type playbooks for web SPA, API service, database, background jobs, offline/local-first, Android, and desktop work
+- technology playbooks for React, Vue, Go, Koa, Laravel, Gin/Templ, MySQL, Postgres, Room, LocalDB, and Rust workspaces
+- composed stack playbooks for browser-only offline SPA, Vue/Koa/MySQL, Vue/Laravel/MySQL, React/Go/Postgres, Go/Gin/Templ/Postgres, Rust fullstack workspace, Android Room offline, WinForms LocalDB, and generic fallback work
+
+These playbooks are baseline-only references. The workflow uses them to guide the scaffold step from owner-private planning before module-by-module implementation continues.
+
+## Development Checks
+
+Run these before packaging changes to the CLI or installed tools:
+
+```bash
+npm run typecheck
+npm run check
+```
+
+`npm run typecheck` uses TypeScript `checkJs` over the package CLI source and shipped `assets/slopmachine` JavaScript utilities without adding a build step. The utility reference lives at `assets/slopmachine/utils/README.md` and documents each installed helper's arguments and output contract.
 
 ### `slopmachine init`
 
@@ -139,45 +134,44 @@ slopmachine init --continue-from P3
 
 What it creates:
 
-- `repo/`
-- `docs/`
-- `.tmp/`
-- `metadata.json`
-- `.ai/metadata.json`
-- `.ai/startup-context.md`
-- hidden `.ai/worktrees/` for parallel git worktrees when used
-- root `.beads/`
-- `repo/AGENTS.md`
-- `repo/CLAUDE.md`
-- `repo/plan.md`
-- `repo/.claude/settings.json`
-- `repo/README.md`
-- `docs/questions.md`
-- `docs/design.md`
-- `docs/api-spec.md`
-- `docs/plan.md`
-- `docs/test-coverage.md`
+- workflow root `.ai/metadata.json`
+- workflow root `.ai/startup-context.md`
+- hidden workflow root `.ai/worktrees/` for parallel git worktrees when used
+- workflow root `.beads/`
+- `task/`
+- `task/.git/`
+- `task/AGENTS.md`
+- `task/CLAUDE.md`
+- `task/.claude/settings.json`
+- `task/repo/`
+- `task/repo/README.md`
+- `task/docs/questions.md`
+- `task/docs/design.md`
+- `task/docs/api-spec.md`
+- `task/.tmp/`
+- `task/metadata.json`
 
 Important details:
 
-- `run_id` is created in `.ai/metadata.json`
-- the workspace root is the parent directory containing `repo/`
-- parent-root `.tmp/` is the audit and fix-check artifact directory used during `P7`
-- parent-root `.tmp/` also holds `test_coverage_and_readme_audit_report.md` after the final post-bugfix audit
-- parent-root `metadata.json` is strict project metadata only and must contain exactly these keys: `prompt`, `project_type`, `frontend_language`, `backend_language`, `database`, `frontend_framework`, `backend_framework`
+- `run_id` is created in workflow root `.ai/metadata.json`
+- the operational session root is `task/`
+- product code lives under `task/repo/`
+- task-root `.tmp/` is the audit and fix-check artifact directory used during `P7`
+- task-root `.tmp/` also holds `test_coverage_and_readme_audit_report.md` after the final post-bugfix audit
+- task-root `metadata.json` is strict project metadata only and must contain exactly these keys: `prompt`, `project_type`, `frontend_language`, `backend_language`, `database`, `frontend_framework`, `backend_framework`
 - `project_type` should use only `fullstack`, `backend`, `android`, `ios`, `desktop`, or `web` when known
-- Beads lives in the workspace root, not inside `repo/`
-- `repo/.claude/settings.json` seeds Claude Code to use the custom `developer` agent by default for that repo
-- planned parallel git worktrees should live under hidden parent-root `.ai/worktrees/` by default so root-level `repo-lane-*` folders do not clutter the workspace
-- when `P5` completes, the workflow moves `repo/plan.md` to parent-root `docs/plan.md`; packaging later validates that `repo/plan.md`, `repo/AGENTS.md`, and `repo/CLAUDE.md` are absent from the delivered `repo/`
-- after non-`-o` bootstrap, the command prints the exact `cd repo` next step so you can continue immediately
-- `--adopt` moves the current project files into `repo/`, preserves root workflow state in the parent workspace, and skips the automatic bootstrap commit
+- Beads lives in the workflow root outside `task/`
+- `task/.claude/settings.json` seeds Claude Code to use the custom `developer` agent by default for that task root
+- planned parallel git worktrees should live under hidden workflow root `.ai/worktrees/` by default so visible task-root folders do not clutter the delivery structure
+- owner-private execution planning lives under workflow root `.ai/plan.md` and is translated into normal developer prompts
+- after non-`-o` bootstrap, the command prints the exact `cd task` next step so you can continue immediately
+- `--adopt` moves the current project files into `task/repo/`, preserves workflow state outside `task/`, and skips the automatic bootstrap commit
 - `--continue-from <PX>` is a smoother alias for existing-project bootstrap; it implies adoption mode and seeds the requested start phase in one step
-- if `--continue-from <PX>` is run while your current working directory is already the real project `repo/`, or if the explicit target path itself points at that `repo/` directory, SlopMachine automatically treats `..` as the workspace root and writes the workflow state there instead of creating `repo/repo`
+- if `--continue-from <PX>` is run while your current working directory is already `task/` or `task/repo/`, SlopMachine automatically resolves the surrounding workflow root instead of creating nested task/repo directories
 - when a later start phase is seeded for adoption or recovery, the Beads workflow phases before that requested phase are created and immediately marked completed so tracker state matches the seeded entry point
 - in the `slopmachine-claude` path, if adopted or resumed later-phase work has no recoverable tracked Claude developer session yet, the owner must launch and orient the needed Claude lane first and only then continue the substantive work in that same session
 - `--phase <PX>` seeds the initial `current_phase` for adoption/recovery bootstrap; the owner should still fall back if the real repo evidence does not support that later phase
-- `repo/plan.md` is seeded at bootstrap and becomes the definitive repo-local execution checklist through planning, development, and `P5`; after `P5`, the preserved reference copy is `docs/plan.md`
+- `task/docs/plan.md` and `task/docs/test-coverage.md` are not seeded or required; planning and coverage notes stay owner-private under workflow root `.ai/`
 
 ### `slopmachine set-token`
 
@@ -222,34 +216,35 @@ slopmachine send-data ses_abc123 --endpoint "https://<project-ref>.supabase.co/f
 
 Where to run it:
 
-- preferred: workspace root
-- also supported: `repo/`
+- preferred: `task/`
+- also supported: workflow root containing `task/`
+- also supported: `task/repo/`
 
-If run from `repo/`, the command resolves the parent workspace root automatically.
+If run from `task/repo/`, the command resolves the surrounding task and workflow roots automatically.
 
 What it exports live:
 
 - owner session from the positional `owner-session-id`
-- developer sessions from `.ai/metadata.json`
-- `beads-export.json` from root `.beads/`
+- developer sessions from workflow-root `.ai/metadata.json`
+- `beads-export.json` from workflow-root `.beads/`
 
 What it includes when present:
 
-- `.tmp/`
+- task-root `.tmp/`
 - `retrospective-<run_id>.md`
 - `improvement-actions-<run_id>.md`
 - `test_coverage_and_readme_audit_report.md`
 
 What it always includes:
 
-- `metadata.json`
+- task-root `metadata.json`
 - `ai-metadata.json`
 - `manifest.json`
 
 Fail-fast conditions:
 
 - missing owner session id argument
-- missing `.ai/metadata.json`
+- missing workflow-root `.ai/metadata.json`
 - missing `run_id`
 - missing tracked developer session ids
 - owner session export failure
@@ -257,7 +252,7 @@ Fail-fast conditions:
 
 Warn-only conditions:
 
-- missing `.tmp/`
+- missing task-root `.tmp/`
 - missing retrospective files
 
 Output behavior:
@@ -343,5 +338,5 @@ slopmachine send-data <owner-session-id> --dry-run --endpoint "https://<project-
 
 - the upload token is machine-level state and is not stored in the repo
 - the owner session id is currently supplied manually to `send-data`
-- developer session ids come from `.ai/metadata.json`
-- broad workflow files and session exports live at workspace root, not inside `repo/`
+- developer session ids come from workflow-root `.ai/metadata.json`
+- broad workflow files and session exports live at workflow root, outside `task/`

package/RELEASE.md

@@ -52,12 +52,12 @@ printf 'console.log("hello")\n' > .tmp-project-continue/index.js
 SLOPMACHINE_HOME="$(pwd)/.tmp-home" node ./bin/slopmachine.js init --continue-from P3 .tmp-project-continue
 ```
 
-7. Test `repo/` auto-wrap for `--continue-from`:
+7. Test `task/repo/` auto-wrap for `--continue-from`:
 
 ```bash
-mkdir -p .tmp-project-continue-parent/repo
-printf 'console.log("hello")\n' > .tmp-project-continue-parent/repo/index.js
-(cd .tmp-project-continue-parent/repo && SLOPMACHINE_HOME="$(pwd)/../../.tmp-home" node ../../../bin/slopmachine.js init --continue-from P3)
+mkdir -p .tmp-project-continue-parent/task/repo
+printf 'console.log("hello")\n' > .tmp-project-continue-parent/task/repo/index.js
+(cd .tmp-project-continue-parent/task/repo && SLOPMACHINE_HOME="$(pwd)/../../../.tmp-home" node ../../../../bin/slopmachine.js init --continue-from P3)
 ```
 
 Note: