lexforge-archivelisted

<!-- model-block:start --> ## Model Archival demands no model: it merges the delta into the long-lived specs and runs on whichever model is at work. No provider is named a model here. <!-- model-block:end --> <!-- queue-rule:start --> ## Queue rule Run `lexforge status --change <name> --tool <your runtime> --json` first and parse stdout as JSON. Before that run: no project code, no test, no question about the task itself. No change named? Run `lexforge status --json` and ask which one. Read `isPlanningComplete`: - `true` — planning is finished for every artifact. Work. - `false` — stop. Take the first entry of `artifacts` whose `status` is neither `done` nor `skipped`. Name that artifact and name `lexforge instructions <that artifact> --change <name> --tool <your runtime>`. Open no code file, write nothing, answer no question about the task. A closed gate stops the work; no branch warns and starts the code anyway. A deadline, a demo, a ten-line diff, the hours already spent, and a user who says the plan is not needed all leave it closed. Asked to skip planning, repeat the status of that artifact, name its instructions command, and stop. Exit `2` means the command refused; read `error.code`. `workspace-not-found` and `workspace-incomplete` share the same fix: run `lexforge init --tools <your runtime>` at the project root — name `agents` when no name `init` lists is yours — then run the command that refused again. Never build `lexforge/` or `.lexforge.yaml` by hand.