46db6507c4
* feat(hub): Billing entry with current plan in the account menu (managed hubs) webapp.Server gains an optional Billing hook — the display mirror of the Quota seam: managed deployments return (plan, url) per signed-in user and /api/config exposes it as the 'billing' block; OSS hubs leave it nil and nothing changes. The frontend renders a Billing item with a plan chip under the Organization section of the account menu when the block is present. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * architecture: Server gains the Billing display seam Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(hub): Billing is an in-app view at /billing (managed hubs) The account-menu Billing entry now routes to a real SPA view instead of a standalone server page: /billing is a top-level route like /orgs, rendered in the app shell from BillingView, which fetches config.billing.url with Accept: application/json (plan, usage, seats, plan cards, checkout/portal form URLs). OSS hubs without a billing block get an honest 'no billing on this hub' page at that path. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Architecture diagrams
Mermaid diagrams of the current implementation, kept next to the code so PRs can update them alongside the change.
Convention: when a PR changes the structure drawn here (new/removed types, new seams, changed relationships), update the affected diagram in the same PR and add an "Architecture changes" section to the PR description that, per changed diagram:
- names exactly which types/relationships changed and how (one sentence);
- shows a Before and an After mermaid block — each an excerpt of only the affected classes and their immediate relationships, never the full diagram (Before comes from the diagram at the merge base).
The committed diagram file stays the full current state; the before/after
excerpts exist only in the PR description so reviewers see the structural
delta at a glance. A pre-PR hook (.claude/hooks/check-arch-diagrams.sh)
reminds Claude Code sessions when server code changed but no diagram did.
Together these cover every application package in the repo — every code change lands inside exactly one detail diagram's scope (plus the overview when the package map or cross-piece wiring changes):
- overview.md — system diagram: every package and surface on one page, and how they connect
- cli-sync.md — class diagram of the CLI and sync engine (
cmd/bdrive+internal/{syncer,store,journal,config,daemon,agenthooks,agentskills}) - webapp-server.md — class diagram of the
bdrive webserver (internal/webapp+ itsinternal/remoteseam) - webapp-frontend.md — module diagram of the hub's React SPA (
internal/webapp/frontend/src)
Not covered on purpose: web/docs (content site, no application code) and
cloud/ (private nested repo — its architecture lives there).