Port upstream skill scripts into v2.4.1: deterministic workflow steps run as Node scripts beside each SKILL.md (specs, pathfinder, feedback payload, commit message, review scope, agent files, handoff path) with tests, the prompt limit rises to 20,000 chars, upstream review fixes are folded in (linked agent files never overwrite AGENTS.md, review stops with no base, paste-safe commit commands, Pathfinder number high-water mark and dry runs), and web console workspace folders are remembered per project and spec, with Finalize forgetting an archived spec's list

AI Assisted
This commit is contained in:
jparkerweb committed 2026-10-04 12:17:05 -07:00
1 parent 5cbc6edce2
commit 7d54941b75
243 files changed
+23698 -1607

No files matched your search

+14 -2
View File
@@ -324,8 +324,20 @@ context for this console session.
Code with a copyable `/add-dir <path>` to run); *Inside another folder in
the list* for a nested one.
The workspace carries across skills you start from the dashboard and back. A
new console session starts with just the folder you started in.
The workspace carries across skills you start from the dashboard and back, and
it is remembered for next time:
- **Saved on every change**, in `~/.plan2code/console/workspaces.json` (beside
`looks.json`, never in the project, since the paths are your machine's),
keyed by the folder you started in.
- **One list per spec.** *Start from scratch* on the dashboard shows the
project's list. Picking a spec loads its own; the first time, it starts as a
copy of the project's, and after that the two are separate. A spec created
mid-run (Pathfinder, Plan) takes the list in force with it. The line under
the dialog's title says whose list it is.
- **Forgotten on archive.** Finalize's Spec Cleanup step says it will forget
the spec's list and runs `console.mjs forget --spec specs/<name>` after the
move.
### Session meter