`.yolo/tick-prompt.md`

72 lines
# LAI yolo tick — one focused change, then exit

You are firing inside an autonomous launchd loop on Mac2. Each fire is an
independent Claude CLI session with NO memory of previous ticks — read the
git log for history.

WORK DIR: /Users/stevestudio2/Projects/lifestyle-asset-intel
PG:        PGHOST=/tmp PGDATABASE=lifestyle_asset_intel
PM2:       lai-server on :9820 (restart with `pm2 restart lai-server`)
TESTS:     `PGDATABASE=lifestyle_asset_intel npm test`  (currently 44/44 green)

## Standing rules (read MEMORY.md if any doubt)

- Local-only ops. NO DNS, NO email, NO scraping eBay (TOS gated), NO outbound
  comms, NO touching dw_unified or any non-LAI repo.
- Always stay legal for scraping — auction houses (Sotheby's/Christie's
  editorial) are public records and OK; aggregators need TOS check first.
- Author email steve@designerwallcoverings.com on every commit.
- `git commit` only if `npm test` passes. One logical change = one commit.
- Reversible only — no `git push --force`, no destructive ops.
- Per Steve's "build and look anywhere for data" + "always stay legal":
  Tier-1 auction house editorial > public datasets > nothing.

## What to do this tick

1. `git log --oneline | head -20` — see what's been done. Don't repeat.
2. Read ROADMAP.md briefly. Pick ONE achievable item.
3. Implement. Test. If `npm test` green, commit. Else revert and pick a
   smaller scope.
4. Restart pm2 if runtime code changed. Don't restart if only docs/SQL.
5. Write a one-line status to `.yolo/yolo-loop.log` then exit.

## Reasonable next items (pick whichever fits a single tick)

- Christie's editorial scrape — mirror tick #13 pattern, more comps, new source
- Phillips / Bonhams / Heritage Auctions — same pattern
- Asset detail "exotic" badge (1-line CSS + EJS conditional)
- /api/family (no slug) — list all families
- Server-side sort param on /api/assets (mirrors q param)
- Condition_facets render on asset detail page
- Sparkline Y-axis labels
- Source.weight-aware similarity weight (replace constant 0.18)
- Add an /admin/audit HTML view over /api/audit/recent
- Methodology version bump trigger when breakdown weights change

## Hard turn budget — BUDGET YOUR EFFORT

You have 25 turns total. Burn-down plan:

  turns 1-3   : read git log, ROADMAP, decide ONE small target
  turns 4-15  : implement (read files, edit, write)
  turns 16-19 : run npm test, restart pm2 if needed, fix small breakage
  turns 20-22 : git add + git commit
  turns 23-24 : log status, exit
  turn 25     : EMERGENCY ONLY — already over budget, abort cleanly

If you reach turn 18 without a working diff, REVERT and pick a smaller
target. Do not keep digging.

If tests are failing on entry to turn 16, revert your edits with
`git checkout -- <files-you-edited>` (NEVER `git clean -fd` on tracked
files). Better to ship nothing than to ship red. Other yolo ticks will
pick the slack.

## Exit conditions

- Tests fail after your changes and < 5 turns left → revert, log, exit.
- Project in broken state on entry → fix-first only, no new features.
- Done with one logical commit → exit cleanly so launchd can fire next.

KEEP IT SMALL. Many small ticks > one large stuck tick.