Commit 7b02bfd
chore: bump to 0.5.5 for
Patch: one new CLI command and its validation fixes (#182, #183). No schema
change, no rail change, nothing that alters what the agent trades or when.
`keel rules add --kind --product --params` inserts one rule row at status
`candidate` -- the lifecycle floor -- so a scout-produced parameter set can
reach `keel rules backtest` / `keel simulate`. Before this, `rules seed` built
rows only from constructor defaults and no CLI accepted params, so a proposal
had no path to evidence without hand-writing Python against
`Repository.insert_rule`.
Status is a literal at the single insert, with no flag and no override: a row
this command creates must still clear `rules backtest` and `rules promote`
before it can reach `paper` or `live`. That property is what makes a write
path into the `rules` table safe to add at all, and it is mutation-tested.
#183 closes the validation gap #182 shipped with. Container params
(`{"oversold": [1,2]}`) and typo'd Literal choices (`entry_zone: "banana"`)
were accepted, stored and rebuilt cleanly, then either crashed the backtest
the row exists for or -- worse -- silently selected a different code path:
`entry_zone: "banana"` falls through to `ema_band`, so the operator sees
`ema_band`'s numbers while believing they measured `ema_touch`, and
`rules promote` re-runs against that same stored row.
uv.lock relocked in the SAME commit, per 0.5.0-0.5.4. Verified with
`uv sync --frozen`, which accepted the lock and rewrote nothing.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>keel rules add (#184)1 parent 861dd18 commit 7b02bfd
6 files changed
Lines changed: 10 additions & 10 deletions
File tree
- packages
- keel-broker-api
- keel-broker-coinbase
- keel-broker-fake
- keel-core
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments