turn-limted feature added
This commit is contained in:
parent
701c7594fd
commit
4bd4f16633
@ -76,19 +76,28 @@ _Goal: all three sub-skills work via `/skill:elicit` etc._
|
|||||||
### Phase 3: Test with turn-limit extension (TDD)
|
### Phase 3: Test with turn-limit extension (TDD)
|
||||||
_Goal: use distill → propagate on real code, verify allium produces useful output._
|
_Goal: use distill → propagate on real code, verify allium produces useful output._
|
||||||
|
|
||||||
- [ ] Checkout turn-limit into this workspace
|
- [x] Checkout turn-limit into this workspace
|
||||||
```
|
```
|
||||||
git clone https://gitea.apps.sustainabledelivery.com/QWAN/monotonic-pi-extensions.git turn-limit-repo
|
git clone https://gitea.apps.sustainabledelivery.com/QWAN/monotonic-pi-extensions.git turn-limit-repo
|
||||||
ln -s turn-limit-repo/packages/pi-turn-limit turn-limit
|
ln -s turn-limit-repo/packages/pi-turn-limit turn-limit
|
||||||
```
|
```
|
||||||
- [ ] Run `/skill:distill` against `turn-limit/` — extract a `.allium` spec from existing code
|
- [x] Run `/skill:distill` against `turn-limit/` — extract a `.allium` spec from existing code
|
||||||
- [ ] Review the generated spec: does it capture turn-limit constraints, enable/disable, UI separation?
|
- [x] Review the generated spec: does it capture turn-limit constraints, enable/disable, UI separation?
|
||||||
- [ ] Run `/skill:propagate` against the generated spec — generate test suggestions
|
- Fixed: section order (entities before config), `session.max_turns` → `config.max_turns`, missing closing brace
|
||||||
- [ ] Write at least one test based on propagate output (TDD red step)
|
- [x] Run `/skill:propagate` against the generated spec — generate test suggestions
|
||||||
- [ ] Implement to make the test pass (green step)
|
- Generated 30 test obligations: 10 unit (P1-P5, C1-C5), 20 integration (E, R, S, W, I, C6-C8)
|
||||||
- [ ] Iterate: use allium to identify more test obligations, write them, make them pass
|
- Identified discrepancy: `checkTurnLimit` uses `>` but handler uses `===`
|
||||||
- [ ] Run `/skill:elicit` to explore the "disable turn limit" feature requirement
|
- [x] Write at least one test based on propagate output (TDD red step)
|
||||||
- [ ] Generate spec + tests for the new feature via propagate
|
- Wrote 21 tests: P1-P5 (pure fn), C1-C8 (config+command), E1-E3 (entity state), R1-R5 (rule)
|
||||||
|
- All pass — green from the start since code already exists
|
||||||
|
- [x] Implement to make the test pass (green step)
|
||||||
|
- Only change needed: exported `getMaxTurns` for testability
|
||||||
|
- [x] Run `/skill:elicit` to explore the "disable turn limit" feature requirement
|
||||||
|
- Elicited 3 design decisions: (1) unlimited = no boundary check, (2) hard reset on re-enable, (3) config value not entity state
|
||||||
|
- [x] Generate spec + tests for the new feature via propagate
|
||||||
|
- Updated spec with `max_turns: Integer | unlimited` and `LimitReEnabled` rule
|
||||||
|
- Propagate generated 13 test obligations; wrote 8 covering config, command, rule, and integration
|
||||||
|
- TDD cycle complete: red (8 failing) → implemented unlimited mode → green (29/29 pass)
|
||||||
|
|
||||||
### Phase 4: Fold in allium rules content
|
### Phase 4: Fold in allium rules content
|
||||||
_Goal: pi agent knows allium syntax rules when editing .allium files._
|
_Goal: pi agent knows allium syntax rules when editing .allium files._
|
||||||
|
|||||||
1
turn-limit
Symbolic link
1
turn-limit
Symbolic link
@ -0,0 +1 @@
|
|||||||
|
turn-limit-repo/packages/pi-turn-limit
|
||||||
Loading…
x
Reference in New Issue
Block a user