ATProto-based AI Assistant Chat interface.

19 files

· Cover the web UI spec's acceptance criteria with tests and tick them off. New tests cover the server redirecting signed-out users before rendering, a viewer being sent from the settings to the login page while a shared chat still opens for them, creating a chat, uploading a PDF and sending it as an attachment part, scrolling to the bottom on send, syncing in a message written from another client, deleting an API key, and the background sync switch. The tool details test now checks that each summary is collapsed. · 3w ago

admin-plugins.md

Group the web app's code by feature. Each folder in src/features (auth, chat-list, conversation, sharing, models, settings, admin) holds that feature's pages, layouts included, components, hooks, lib, and queries, and the routes stay thin, rendering a feature's page. Page files are named after the component they export. The query factories split from src/queries.ts into each feature's queries.ts, leaving staleTime in src/shared, which also holds the API client, errors, search params, and the schema forms that admin and settings share. inheritedModel moves from the models module to the conversation's branch module, so models no longer depends on the conversation. Tests mirror the new tree, and the specs, the architecture doc, and CLAUDE.md name the new paths.

admin-settings.md

Group the web app's code by feature. Each folder in src/features (auth, chat-list, conversation, sharing, models, settings, admin) holds that feature's pages, layouts included, components, hooks, lib, and queries, and the routes stay thin, rendering a feature's page. Page files are named after the component they export. The query factories split from src/queries.ts into each feature's queries.ts, leaving staleTime in src/shared, which also holds the API client, errors, search params, and the schema forms that admin and settings share. inheritedModel moves from the models module to the conversation's branch module, so models no longer depends on the conversation. Tests mirror the new tree, and the specs, the architecture doc, and CLAUDE.md name the new paths.

Group the web app's code by feature. Each folder in src/features (auth, chat-list, conversation, sharing, models, settings, admin) holds that feature's pages, layouts included, components, hooks, lib, and queries, and the routes stay thin, rendering a feature's page. Page files are named after the component they export. The query factories split from src/queries.ts into each feature's queries.ts, leaving staleTime in src/shared, which also holds the API client, errors, search params, and the schema forms that admin and settings share. inheritedModel moves from the models module to the conversation's branch module, so models no longer depends on the conversation. Tests mirror the new tree, and the specs, the architecture doc, and CLAUDE.md name the new paths.

Implement initial buildout of core features.

Merge main, bringing in the admin area from admin-ui: settings in the database instead of config.yml, roles, registration and access with viewers and suspension, plugin instances, and admin models. The server merges as is, apart from three fits to this branch: app.ts passes the app name from the settings store to Start with each request, in place of admin-ui's index.html templating; the viewer sign-in check looks for this branch's /shared/ links instead of /s/; and the development URL is port 3000, where the server serves the web app.

browser-store.md

Add local full-text search with search-as-you-type; open results on the matching branch

chat-storage.md

Add the admin area for settings to replace config.yml.

Add the admin area for settings to replace config.yml.

encrypted-conversations.md

Add admin and encryption specs to the repo.

Group the web app's code by feature. Each folder in src/features (auth, chat-list, conversation, sharing, models, settings, admin) holds that feature's pages, layouts included, components, hooks, lib, and queries, and the routes stay thin, rendering a feature's page. Page files are named after the component they export. The query factories split from src/queries.ts into each feature's queries.ts, leaving staleTime in src/shared, which also holds the API client, errors, search params, and the schema forms that admin and settings share. inheritedModel moves from the models module to the conversation's branch module, so models no longer depends on the conversation. Tests mirror the new tree, and the specs, the architecture doc, and CLAUDE.md name the new paths.

Merge main, bringing in the admin area from admin-ui: settings in the database instead of config.yml, roles, registration and access with viewers and suspension, plugin instances, and admin models. The server merges as is, apart from three fits to this branch: app.ts passes the app name from the settings store to Start with each request, in place of admin-ui's index.html templating; the viewer sign-in check looks for this branch's /shared/ links instead of /s/; and the development URL is port 3000, where the server serves the web app.

Add the admin area for settings to replace config.yml.

Judge a NAT64 address by the IPv4 address inside it, rather than refusing the whole 64:ff9b::/96 range as private. On an IPv6-only network, DNS64 gives every IPv4-only host a NAT64 address next to its IPv4 one, and the guard refuses a host when any of its addresses is private. So sign-in failed at the callback, with "Refusing to connect to private network address 64:ff9b::d8c6:4f01", since resolving the identity reached the PDS, the handle, and plc.directory through the guard. Every other guarded fetch failed the same way. A NAT64 address hiding a private IPv4 address, like 64:ff9b::7f00:1 for 127.0.0.1, is still refused.

Merge main, bringing in the admin area from admin-ui: settings in the database instead of config.yml, roles, registration and access with viewers and suspension, plugin instances, and admin models. The server merges as is, apart from three fits to this branch: app.ts passes the app name from the settings store to Start with each request, in place of admin-ui's index.html templating; the viewer sign-in check looks for this branch's /shared/ links instead of /s/; and the development URL is port 3000, where the server serves the web app.

Update the specs and ADR 0001 for the dev wiring and the renamed routes.

Merge main, bringing in the admin area from admin-ui: settings in the database instead of config.yml, roles, registration and access with viewers and suspension, plugin instances, and admin models. The server merges as is, apart from three fits to this branch: app.ts passes the app name from the settings store to Start with each request, in place of admin-ui's index.html templating; the viewer sign-in check looks for this branch's /shared/ links instead of /s/; and the development URL is port 3000, where the server serves the web app.

Implement initial buildout of core features.

Group the web app's code by feature. Each folder in src/features (auth, chat-list, conversation, sharing, models, settings, admin) holds that feature's pages, layouts included, components, hooks, lib, and queries, and the routes stay thin, rendering a feature's page. Page files are named after the component they export. The query factories split from src/queries.ts into each feature's queries.ts, leaving staleTime in src/shared, which also holds the API client, errors, search params, and the schema forms that admin and settings share. inheritedModel moves from the models module to the conversation's branch module, so models no longer depends on the conversation. Tests mirror the new tree, and the specs, the architecture doc, and CLAUDE.md name the new paths.

Cover the web UI spec's acceptance criteria with tests and tick them off. New tests cover the server redirecting signed-out users before rendering, a viewer being sent from the settings to the login page while a shared chat still opens for them, creating a chat, uploading a PDF and sending it as an attachment part, scrolling to the bottom on send, syncing in a message written from another client, deleting an API key, and the background sync switch. The tool details test now checks that each summary is collapsed.

README.md

Specs #

Each file here describes one feature of SCN Chat: what it does, why it exists, how it is built, what it deliberately leaves out, and how to tell it works. A spec is written and agreed on before the feature is built, and kept current as the feature changes.

Specs are the source of truth for behavior. When code and spec disagree, one of them is wrong, and the fix is to bring them back in line rather than let them drift. A spec should be detailed enough that someone, or an LLM, could rebuild the feature from it plus the project's CLAUDE.md.

These files are all AI generated and maintained.

The overview at the end of this file lists every spec and whether it is active, planned, or done.

Sections #

Summary: what the feature does, for someone meeting it for the first time.
Motivation: the problem it solves, with enough context to make good judgment calls.
Design: the technical approach, data shapes, and where the code lives.
Scope Boundaries: what the feature does not do.
Edge Cases and Decisions: a running log of non-obvious choices.
Acceptance Criteria: checks that each become at least one test.
Files: the code that implements the feature, used to spot specs that have fallen behind the code.

Overview of Feature Specs #

Active #

[[web-ui]]: rebuilding the web app on TanStack Start inside Hono, at parity with its acceptance criteria. Phase 1 of the web rebuild.

Planned #

The later phases of the web rebuild, each spec written before its phase starts:

[[extending]]: the web app made easy to change in a fork, with tables of part and tool views, tool status and steps, message actions as a list with Copy, a Markdown seam with code block copy, smaller components, and a guide in docs/extending.md.
styling: the styling stack, a theme of design tokens for light and dark, and the designer's default look.

Other features:

[[encrypted-conversations]]

Completed #

Phase 1, initial build-out, implemented and tested, awaiting a check against a real spaces PDS:

[[foundation]]
[[plugins]]
[[auth]]
[[chat-storage]]
[[providers]]
[[chat-turns]]
[[attachments]]
[[titles]]
[[sharing]]
[[browser-store]]

After the initial build-out:

[[search]]
[[web-search]]
[[admin]]
[[admin-plugins]]
[[admin-settings]]