Wire the app like the boilerplate: door, queue, schedules, eight tabs

app/main.py assembles it in the boilerplate's order, auth.connect first,
then the queue with the scheduler and the pages. TABS is Roles,
Applications, Agents, Companies, Jobs, Schedules, Messages and Account:
the alpha page's three views become templates on the boilerplate's
base.html, driven by static/roles.js (the old app.js) through api() and
toasts.js, over the unchanged JSON routes. Companies lists every board with
its open roles and the affinity control. A 422 is one sentence, so a toast
never reads [object Object].

Config takes the boilerplate's shape: APP_CONFIG or config.yaml, a missing
file is the defaults, an unknown key is an error. roles.yaml is gone;
config.yaml is the committed default and carries the starter agents.

pull is now a job that asks for the pull cascade, because a schedule
enqueues a job kind; its default schedule, every 6h, is declared beside it
in app/jobs/cascade.py. pull_batch's targets are keyword-only so the Jobs
tab offers no batch button. `app worker` is the boilerplate's; `app job`
still drains a queue of its own and fires no schedules.

test_coupling holds pipeline, auth and desk apart (desk may import
pipeline) and plugins to desk; test_architecture keeps app's layers, now
with main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Opus 5.5 committed 2026-09-23 12:48:12 +02:00
1 parent 24508dd6fc
commit 59a301c351
42 files changed
+2407 -998

No files matched your search

+11 -6
View File
@@ -1,14 +1,19 @@
"""roledesk: a job-search engine on the `desk` plugin contract and the `pipeline` queue.
Layers, bottom to top, each importing only from those below it (see
uv run app serve
The package is `app` because the boilerplate's deploy kit assumes it. Layers,
bottom to top, each importing only from those below it (see
`tests/test_architecture.py`):
models the shapes handed round, and the key functions for clustering
config `roles.yaml`, validated
config `config.yaml`, validated
storage `Store`: every SQL statement against `roledesk.db`
jobs the work this app queues
web the FastAPI app
cli the entry point
jobs the work this app queues, and its default schedule
web the tabs and the JSON routes behind them
main `create_app()`: the door, the queue, the pages, in that order
cli `app serve`, `app job`, `app worker`, `app companies`, `app db`
`desk` and `pipeline` come from the news repo and are imported, never edited.
`pipeline/`, `auth/` and `desk/` are downstream copies (of the boilerplate and
of news) and import nothing from here; `tests/test_coupling.py` holds that.
"""