chore(deploy): sync live-rules.json with the live rule set (#855)

[eaitbrahim]

Closes #855

Regenerates deploy/live-rules.json from the live rule set. I made a read-only copy of ~/keel/keel-live.db with Python's sqlite3 backup API (source opened mode=ro) into a scratch dir, and ran scripts/rule_manifest.py export against that copy. Nothing under ~/keel was written.

Live DCA rules (status live)

id	product	budget per buy	cadence
6	BTC-USD	$40	7 days
8	ETH-USD	$25	7 days
9	PAXG-USD	$25	14 days
10	ADA-USD	$15	14 days
11	XLM-USD	$15	14 days
12	DOGE-USD	$15	14 days
13	FET-USD	$15	14 days

All seven have dip_bonus_pct 0 and lookback_days 90.

The turtles are paper. The six turtle_breakout rules (BTC, ETH, PAXG, ADA, XLM, DOGE) are status: paper. The old manifest listed five of them as live.

Rulings

• Updated test_committed_manifest_is_valid. It pinned exactly one DCA rule and pinned that rule's params to Dca's constructor defaults. The regenerated manifest breaks both: there are 7 DCA rules, and none uses the default $50. The test comment itself says to update it when this happens. It now asserts:
  • every DCA rule is live;
  • no rule is candidate;
  • every DCA rule differs from the constructor defaults on at least one param, so a keel init reseed would show as a change in value, not only a change in status.
  • Why: the brief expected the test to pass as-is (fix(executor): size each DCA buy from the rule's own amount (#840) #843/test_rule_manifest still pins the DCA rule budget to config.dca.budget_usd after #840 #844 dropped the budget pin), but the count pin and the defaults-coincidence pin were still there.
  • Cost if wrong: one test's assertions need re-tightening. No runtime effect.
• Refreshed one sentence in scripts/rule_manifest.py's module docstring. It said the live DCA rule is 50 on purpose, matching the default. That is no longer true.
  • Why: keel keeps its rules in docstrings, and a stale one misleads.
  • Cost if wrong: none.

Test evidence

• uv run pytest -q: 7027 passed, 3 skipped (exit 0)
• ruff check keel tests scripts: exit 0
• ruff format --check keel tests scripts: exit 0
• mypy: exit 0
• Mutation checks. For each, I confirmed the file differed from a saved copy before running, then restored it from that copy:
  • set BTC budget_usd to "50", so the rule equals the defaults: the value assertion fails, naming BTC-USD;
  • set one DCA rule's status to paper: the status assertion fails.

🤖 Generated with Claude Code