Factory acceptance phase and issue restart
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
3f39f4bd65
commit
e09e295f60
8 files changed
+246
-8
No files matched your search
@@ -3,6 +3,26 @@
|
||||
All notable changes to CodeCraft. Versions follow [Semantic Versioning](https://semver.org/);
|
||||
until 1.0, minor versions may contain breaking changes.
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- **Factory acceptance phase**: a finished build is checked by a different model. It starts the built
|
||||
branch (as `.factory/setup.json` describes: `install`, `start`, `url`), goes through the acceptance
|
||||
scenarios from the review – kept away from the builder – and uses the browser tool where it can.
|
||||
Every scenario ends as pass, fail or *unverified*; unverified ones are reported openly and never
|
||||
count as passed. One failed scenario sends the issue back to the build with the findings (at most
|
||||
2 rework rounds, then `failed`); otherwise the issue is `done` and the pull request waits for you
|
||||
to merge – the factory never merges.
|
||||
- **Restart an issue** in the factory page (select an issue → "Restart at": review, build or
|
||||
acceptance). Works for failed, rejected, done and waiting issues; restarting at review forgets the
|
||||
stored scenarios, and restarts reset the retry counters.
|
||||
|
||||
### Fixed
|
||||
|
||||
- Factory runs interrupted by a server restart continue where they were (builds in a rework round
|
||||
resume as rework).
|
||||
|
||||
## [v202611-00042] – 2026-11-16
|
||||
|
||||
### Added
|
||||
|
||||
Reference in new issue
Block a user