on_status replaces the single on_pass field with a mapping that routes
each review status (pass/fail/retry/escalate) to a different target
stage. The lookup order for non-pass statuses is:
on_status[status] -> on_fail -> next_stage (agent output)
Config parsing validates that on_status keys are valid status names
and all referenced stages exist. Includes test coverage for parsing,
validation errors, pass/fail/escalate routing, and on_fail fallback.
- Add `integ-test` to create, set up, validate, and run integration template tasks
- Add `integ-report` to summarize latest integration run artifacts
- Switch default pastebin template from model fallback to single `qwen3-coder:30b`
- Support optional Ollama fields: `num_ctx`, `num_predict`, `seed`, and `stop`
- Add `nightshift validate` preflight for task-specific test files
- Update pastebin docs, config reference, and ideas tracking
- Add tests for integration helpers, task-test validation, config parsing, and template expectations
Changed the pastebin tutorial so it now starts skeletal: no prebuilt Flask behavior, no pre-generated task tests, and .gitkeep placeholders under templates/ and tests/. The new pipeline in nightshift/project_templates/tutorial-pastebin/nightshift.yaml:1 now runs:
plan -> semantic_context -> context -> write_tests -> review_tests -> implement -> pytest -> review
────────────────────────────────────────────────────
Added nightshift/project_templates/tutorial-pastebin/.nightshift/agents/test-writer.md:1, tightened the planner/implementer/reviewer/debugger prompts, mirrored the pipeline docs/
example, and raised default retries to 6 for the basic starter plus pastebin.
I also fixed the retry policy issue in nightshift/escalation.py:17 and nightshift/pipeline.py:251: configured repeated-failure thresholds are now respected instead of hard-stopping in nightshift/project_templates/tutorial-pastebin/
early after three same-stage/same-cause failures. Non-implementation file_writer stages now get stage-specific retry artifacts so test generation does not collide with implementation
repair artifacts
- Added nightshift what-happened to summarize the latest run/task failure from artifacts.
- Added integ-run --setup with setup options, so sandbox creation can immediately run integ-setup.
- integ-setup output now explicitly shows the venv activation command.
- Command stages now prefer a detected project/adjacent .venv, so python -m pytest -q should use the integ venv without relying on shell activation.
- Retry command outputs now get attempt-specific artifact names, like test-output-1.txt, instead of overwriting.
- Docs updated in README.md, the pastebin template README, and examples/tutorial/03-pastebin.
- Added pytest config so root python -m pytest -q ignores generated integ/template target tests.
- Version bumped to 0.2.4-alpha-bratwurst-relish.
What changed:
- Added file_writer stage support in nightshift/config.py:93, nightshift/agents.py:446, and nightshift/pipeline.py:374.
- Added file-block parsing and deterministic patch generation in nightshift/patches.py:65.
- file_writer agents now return complete file blocks:
```file:relative/path.py
<complete file content>
```
NightShift reads current files and generates the unified diff itself.
- Existing patch_validator, patch_normalizer, and patch_apply still run after that.
- Switched tiny-lisp-nightshift/nightshift.yaml:51 to type: file_writer.
- Updated tiny-lisp-nightshift/agents/implementer.md:1 to request file blocks instead of diffs.
- Updated README, tutorial, config reference, and design doc.
Also added tests for parsing file blocks, generating multi-file diffs, validating those diffs, and running a full file_writer -> normalize -> validate pipeline.
Verification: python -m unittest discover -v passes, 101 tests.
