feat: 100% a8n.tools parity - SSR frontend, dunite backend, governance conformance #16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/bunyip-dunite-infra-boot"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Brings bunyip to 100% functional parity with a8n.tools (menkent), all on the generic dunite crates, and into full conformance with the governance standard. Backend = real actix-web SaaS + OpenID Provider; frontend = Axum SSR (Dioxus removed). Verified end-to-end. Supersedes this PR's original infra-only scope.
What's here
Verification (host, against Postgres)
Migrations apply; api /v1/health 200; OIDC discovery + JWKS serve the real EdDSA key; /v1/auth/login authenticates the seeded admin; SSR web renders (/, /login, /pricing 200, "PSA Systems") talking to the api. Container builds validated via docker compose config.
Notes
Generated with Claude Code.
feat: boot-verify the dunite backend + wire dev/prod container infrato feat: 100% a8n.tools parity - SSR frontend, dunite backend, governance conformanceThe SSR server uses ServeDir("assets") (CWD-relative), but the dev container CMD built the CSS in /app/bunyip-web then `cd /app` and ran cargo from the repo root, so /assets/styles.css resolved to /app/assets (empty) -> 404, no styling. - Dev Dockerfile: stay in /app/bunyip-web when running cargo-watch so the CWD-relative ServeDir("assets") finds the crate's assets/ (cargo still locates the workspace by walking up). - just run-web: cd into bunyip-web for the same reason on host runs. - Commit bunyip-web/assets/styles.css (un-ignore it), matching menkent, so host runs / fresh clones serve styling without a build step (the dev container + prod image still rebuild it via `bun run build:css`). Verified: GET /assets/styles.css -> 200 text/css (52 KB), landing references it. #BUNYIP-26 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>The SSR port inherited menkent's (a8n.tools) shadcn/orange theme and "PSA Systems / Managed tools" copy. Restores Bunyip's own brand identity, recovered from the original Dioxus frontend. - Theme (input.css): remap the shadcn semantic tokens (background/foreground/primary/secondary/muted/card/border/ring/...) to Bunyip's reed/water green palette so every existing template restyles with no class churn; add the bunyip-reed-* / bunyip-water-* + surface @theme tokens used by the restored landing; Inter + JetBrains Mono fonts; dark + high-contrast variants. styles.css regenerated (reed #2f4e2e, no orange f97316). - Wording: brand "Bunyip" + tagline "Surfaces what matters." in nav/footer; meta description + theme-color metas; landing hero ("The SaaS layer for your PSA"), six feature cards (SSO/billing/orgs/MFA/admin/feedback), and CTAs restored from the original; our-story/pricing/feedback reframed to Bunyip's business-shell-for-Mokosh framing; page-title suffixes "· Bunyip"; startup banner. No handler logic, routes, or API-client code changed. Verified: cargo check -p bunyip-web clean; the running web container rebuilt styles.css in-container; landing serves Bunyip copy + reed theme. #BUNYIP-26 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>