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

+13 -8
View File
@@ -1,10 +1,13 @@
"""The coupling rule, held by reading the imports.
`pipeline/` and `auth/` import nothing from `app/` and nothing from each
other. `app/` imports both. That is what makes each of them copyable on its
own into a project that has never heard of this one -- and it is exactly the
rule that breaks quietly, one convenient import at a time, until the folder is
a port rather than a copy.
The boilerplate's test, with roledesk's two extra folders. `pipeline/`,
`auth/` and `desk/` import nothing from `app/` and nothing from each other,
except that `desk/` is built on `pipeline/`, as it is in news. `plugins/`
imports `desk/` and nothing else, since a plugin is app-agnostic. `app/`
imports all of them. That is what keeps each copied folder a copy that can be
refreshed from its source, and it is the rule that breaks quietly, one
convenient import at a time, until the folder is a port rather than a copy.
`tests/test_architecture.py` holds `app/`'s own layers.
Read with `ast` rather than grepped: a string containing the word `app`, or a
line in a docstring showing what an app would write, is not an import, and a
@@ -21,10 +24,12 @@ import pytest
ROOT = Path(__file__).resolve().parent.parent
#: The module folders and what each may not reach for. Listed rather than
#: derived so that adding a fourth folder is a decision, not an accident.
#: derived so that adding a folder is a decision, not an accident.
FORBIDDEN = {
"pipeline": ("app", "auth"),
"auth": ("app", "pipeline"),
"pipeline": ("app", "auth", "desk", "plugins"),
"auth": ("app", "pipeline", "desk", "plugins"),
"desk": ("app", "auth", "plugins"),
"plugins": ("app", "pipeline", "auth"),
}