Crate pacenotes_server 

Everything but the CLI entry point, so server/tests/ drives the real router and admin commands.

Modules

access_log

One INFO line per response on target access, since production runs at INFO, where TraceLayer says nothing.

admin

The token subcommands. A raw token exists only in mint’s return value; every other command works on its hash.

auth

Who may see a package: bearer token → sha256 → credential row → decision. Raw tokens are never stored or logged; only hash_token of one leaves a request.

db

The libSQL auth database: credentials and their grants, never packages. Queries stay plain SQL so that moving to remote Turso is only a --db-url change.

error

reports

Conflict reports from installers: two selected packages wrote the same file, the later one won, and only the operator can fix the catalogue.

routes

The HTTP surface. Handlers stay thin: access rules live in auth, package lookups in store.

store

The data root: package zips on disk, the generated manifest that lists them, and the message of the day.