Skip to content

Scaffold Cookbook application - #3

Draft
iPior wants to merge 1 commit into
mainfrom
agent/scaffold-cookbook
Draft

Scaffold Cookbook application#3
iPior wants to merge 1 commit into
mainfrom
agent/scaffold-cookbook

Conversation

@iPior

@iPior iPior commented Aug 15, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • replace generic template identity across package metadata, environment examples, Docker aliases, workflow names, API metadata, page metadata, and UI copy
  • add a responsive, consumer-oriented Cookbook shell using the Pior Labs design-system foundation without inventing recipe functionality
  • establish Hono liveness, metadata, PostgreSQL readiness, 404, and error-handling baselines
  • remove the generic example table while retaining Drizzle configuration and safe no-migration behavior until the Phase 1 domain model is approved
  • document the central service-auth configuration contract and exact trusted-client registration requirements without introducing a second auth system
  • retain private production ports, health checks, DATABASE_URL_FILE, shared platform networks, and the static-only web Caddy runtime
  • add a lockfile and use frozen installs in CI and Docker builds
  • rewrite the README and update technical-design/status documentation to reflect the scaffold's actual state

Validation

  • pnpm install --frozen-lockfile
  • pnpm typecheck
  • pnpm build
  • pnpm db:generate (zero tables; no migration generated)
  • pnpm db:migrate (expected no-op without a migration journal)
  • built API smoke check for /health, /api, and 404 behavior
  • local and production docker compose ... config --quiet
  • desktop and mobile visual QA of the production web build
  • git diff --check
  • scans for stale package/template identifiers, .ts.szarans.ca hostnames, and common credential patterns

The repository does not currently define lint or test commands, so there were no lint or test suites to run.

External follow-up

Before authenticated feature work or production deployment:

  1. Register and seed a trusted cookbook client in service-auth with production URI https://cookbook.szarans.ca, production callback https://cookbook.szarans.ca/api/auth/oauth2/callback/auth-pior, local callback http://localhost:5175/api/auth/oauth2/callback/auth-pior, and scopes openid profile email offline_access.
  2. Provision the Cookbook database, role, server-managed database connection file, shared-network routes, and cookbook.szarans.ca split-horizon DNS in platform-deploy.
  3. Configure the repository production environment, APP_ENV secret, and DEPLOY_DIR variable before enabling automatic deployment.

Intentionally deferred

The Phase 1 domain schema, auth/session implementation, image storage, search, validation rules, and API boundaries remain unresolved in the unapproved technical design. This PR does not implement recipe features, later product phases, or MCP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant