Files
jobboard/docs/open.md
T
WolfandClaude Sonnet 471ace703c Switch the extract and summarise stages on the page, over config.yaml
A stored `stage:extract` / `stage:summarise` in the state table overrides
extract.enabled / summarise.enabled; with none, the file applies. One
function, stages.stage_on, decides, and both tasks' finders ask it.
GET/PUT /api/stages and `app stages` show and set it with who would answer;
Runs has a "What the model reads" block, and a search agent's card says when
a stage is off and links to the switch.

Co-Authored-By: Claude Sonnet <noreply@anthropic.com>
2026-09-29 15:54:53 +02:00

1.7 KiB

Open

What is left after the phone rework of 2026-09-25, for whoever picks the repo up next, in the order it bites.

  • The checkout moved. CLAUDE.md, README.md, desk/README.md and the refresh commands assume ../boilerplate and ../news beside the checkout. Keep them beside it in the sandbox or change the paths. .venv holds absolute paths, so uv sync --all-extras again after the move.
  • The boilerplate moved on. Since roledesk's last refresh (77052a8, the schedules fix) it has 4573f6d (the kit: the layout patterns every app built for itself, as classes) and 1679e88 (deploy from a WSL checkout, the sandbox setup). Refresh deploy/ and pipeline/ with git archive, and see whether app/static/app.css should use the kit's classes instead of its own copies of the same rules.
  • Restart the server. A server started before the rework runs the old code; on start the database migrates to schema v4 (vote, summary, article text on roles).
  • The live database has two agents, "Berlin backend" and "Remote EU stretch", so Ranking edits the first and the Roles order menu lists both by name. Delete one with the CLI for a plain Best match.
  • Summarising is off until the switch under Runs (default summarise.enabled: false) is used, and needs a model backend, as extract does. The Summarise button on a read page works either way once a backend is configured.
  • Ranking's gates are still a JSON box under Advanced. A form (country list, remote require or prefer) is the next step there.
  • Votes do not train fit. A vote only moves the rank at read time. Feeding votes into the intent vector is worth doing once there are a few hundred.