Merge remote-tracking branch 'origin/main'
This commit is contained in:
commit
063771d617
3 files changed
+20
No files matched your search
@@ -32,3 +32,11 @@ The package is `app`, following the boilerplate: the deploy kit, `APP_CONFIG`, `
|
||||
# Rule:
|
||||
|
||||
`pipeline/`, `auth/` and `deploy/` are downstream copies of `../boilerplate`, `desk/` of `../news`. They are refreshed with `git archive`, and a fix lands upstream first, otherwise the next refresh reverts it.
|
||||
|
||||
# Rule:
|
||||
|
||||
Phone and UI patterns come from `../news` (`newsdesk/web/templates/index.html`, `newsdesk/web/static/app.css`) and `../health` (`webapp/`), which went through the phone fixes already; the boilerplate has none. Copy their fragments, do not write new ones.
|
||||
|
||||
# Rule:
|
||||
|
||||
A larger rework is planned first, as a doc in `docs/` committed on main with work packages that own disjoint files, then built by Opus and Sonnet agents in parallel worktrees and merged into main by the planner. The plan is folded into `decisions.md` and deleted when the work lands.
|
||||
@@ -52,5 +52,6 @@ The reader, `/roles/{uid}`, shows the full posting: the same vote and Save contr
|
||||
## Docs
|
||||
|
||||
- [`docs/decisions.md`](docs/decisions.md): what was decided for roledesk and why.
|
||||
- [`docs/open.md`](docs/open.md): what is left to do, for whoever picks this up next.
|
||||
- [`desk/README.md`](desk/README.md), [`pipeline/README.md`](pipeline/README.md), [`auth/README.md`](auth/README.md), [`deploy/README.md`](deploy/README.md): the copied modules, where each comes from and how to refresh it.
|
||||
- [`docs/hosting.md`](docs/hosting.md), [`docs/release.md`](docs/release.md), [`docs/server.md`](docs/server.md), [`docs/password-protection.md`](docs/password-protection.md), [`docs/llm-backends.md`](docs/llm-backends.md): the boilerplate's deployment docs.
|
||||
@@ -0,0 +1,11 @@
|
||||
# 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** (`summarise.enabled: false`) 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.
|
||||
Reference in new issue
Block a user