Files
jobboard/app/templates/account.html
T
WolfandClaude Opus 5.5 59a301c351 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>
2026-09-23 12:48:12 +02:00

21 lines
1.0 KiB
HTML

{% extends "base.html" %}
{% block title %}Account — roledesk{% endblock %}
{% block content %}
<h1>Account</h1>
<p class="lede">One password, the sessions it has opened, and the passkeys registered beside it. There is no user to create and none to delete, because there is one. <code>docs/password-protection.md</code> is the reasoning behind every choice on this page; <code>auth/README.md</code> is how to take the folder into another project.</p>
<section class="card">
{# As on the Jobs and Schedules tabs: the element and its script belong to
the module, so this page is two lines and `auth/` owns what they draw.
It says its own failures in place, beside the button that caused them,
and raises `auth-account:error` with the server's `detail` as well. No
toast is wired to that here on purpose: one failure said twice is worse
than one failure said once, and next to the form is where it belongs. #}
<script type="module" src="/_auth/account.js"></script>
<auth-account></auth-account>
</section>
{% endblock %}