Skip to content

feat(web): add authenticated Next.js demo host - #788

Draft
behinddwalls wants to merge 2 commits into
preetam/codex/web-library-corefrom
preetam/codex/web-demo-host
Draft

behinddwalls wants to merge 2 commits into
preetam/codex/web-library-corefrom
preetam/codex/web-demo-host

Conversation

@behinddwalls

@behinddwalls behinddwalls commented Oct 6, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Why?

The library needs a demoable reference application that owns framework lifecycle, authentication, upstream connectivity, and deployment.

What?

Add the Next.js shell, local HTTP Basic authentication with username test and a configured nonempty password, server-side h2c/TLS gateway transport validation, readiness checks, dynamic rendering, refresh integration, styling, and Bazel standalone/OCI targets. The local test/test credential convention is demo-only; production authentication remains out of scope. Business routes are introduced in subsequent PRs.

Test Plan

Repository-native validation passed: make test (141 targets), make lint, make check-tidy, and make check-gazelle. The web generation, lint, typecheck, unit/component, and package-consumer checks passed on the complete stack. The production Next standalone/OCI build passed; host tests cover accepted/rejected credentials, readiness failures, and transport configuration.

Stack

  1. docs(web): design gateway-backed web library #749
  2. build(web): add Bazel workspace and generated gateway API #786
  3. feat(web): add framework-independent presentation library core #787
  4. @ feat(web): add authenticated Next.js demo host #788
  5. feat(web): add queue directory and live request list #789
  6. feat(web): add request summary and lifecycle history pages #790
  7. feat(web): add readable change submission history pages #791
  8. test(web): wire local demo and real-stack browser checks #792
  9. feat(web): discover configured queues through the gateway #793

## Summary

### Why?

The reusable library needs a reference host that owns framework behavior, authentication, gateway connectivity, and deployment.

### What?

Add the Next.js shell, Basic authentication, server-side h2c/TLS transport validation, readiness checks, host-supplied refresh transitions, styling, and Bazel standalone/OCI targets. Business pages are introduced in subsequent changes.

## Test Plan

Passed nine API/library/host check targets and the production Next standalone build. Passed repository formatting, lint, module tidy, and Gazelle checks.
## Summary

### Why?

Local testing needs the requested test/test login rather than a long demo password.

### What?

Use test as the Basic-auth username and permit nonempty demo passwords while still rejecting missing configuration and invalid credentials.

## Test Plan

Passed web checks and all four real-stack browser tests with test/test credentials.

This branch has not been deployed

No deployments
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