* docs: add Northstar capabilities walkthrough and update Studio flow
* docs: show authorization results and simplify workflow guidance
* docs: align quick-start prompt with the demonstrated business pages
* docs: link account and session management from authentication overview
* docs: use current blue sign-in screenshot in authentication overview
* docs: align sign-in page reference with updated overview
* docs: present password sign-in before login customization
* docs: explain business needs before capability prompts
* docs: describe general capability needs and emphasize example outcomes
* docs: remove duplicate account result emphasis
* Update the plugins, templates and UI Library for the new runtime
Device authorization, scoped API keys, service accounts, user invitations and preferences, secrets-backed credentials, the inbox and the cn package across the existing plugins, examples and the three templates, with the UI Library's auth, inbox, authorization and component items.
* Declare the UI Library site's favicon
* Use the NocoBase favicon on the UI Library site
* Fix generated-app shell tests and the Hub's user deletion test
Inline the authentication client in the templates' Vitest config so its guards share the test's react-router, and update the Hub test to the users plugin's new copy and spinner label.
Encrypted secrets, a command manifest derived from the API document, environment-variable manifests, sample data and on-demand Apps in the runtime, plus the new agent protocol, application CLI client, agent runner and Docker App Host packages.
Replace the single `page:ai.settings` grant with seven settings items under
System management → AI, one per settings page: `ai.employees`,
`ai.llmServices` and `ai.mcpServers` with `read` and `manage`, and
`ai.skills`, `ai.tools`, `ai.usage` and `ai.conversations` with `read`.
Every management route names the permissions it accepts, pages open with
`read` and turn their controls off without `manage`, and previewing another
user's AI file requires `read` on `ai.conversations`.
A migration gives every item and action to each Permission Set that held the
page grant. A grant of every page no longer opens the AI settings.
Remove the management routes no settings page called: employee templates,
create and delete, skill and tool writes, single LLM service and MCP server
reads, and both MCP connection tests. The package moves to the 3.0.0
prerelease line.
Generates an OpenAPI 3.1 document for every application at GET /api/swagger and serves Swagger UI at GET /api/swagger/docs to signed-in users and API keys. Every hand-written /api route is declared or explicitly hidden, data endpoints are documented per field, Better Auth's endpoints are merged, routes behind runtime dispatchers are registered generically, and pnpm openapi:check enforces the declarations in CI. All changed packages carry changesets.
* refactor(templates): build the sidebars from shadcn Sidebar primitives
Replace the hand-rolled LayoutSidebar and NavigationTree in the default,
examples and hub templates with shadcn's Sidebar, keeping the collapsed
menu behaviour from #317: zero-delay tooltips, hover and keyboard-focus
popovers with permission-filtered children, nested expansion, parent
navigation and the selected group's highlight.
components/ui/sidebar.tsx stays as the shadcn CLI writes it. The layouts
customize it from outside: widths through the provider style in spacing
units, a phone Sheet with a translated title rendered by app-sidebar.tsx,
and a document keydown listener that keeps Ctrl/Cmd+B from reaching the
provider's window listener.
Claude-Session: https://claude.ai/code/session_01KLvKwu4oUSHnFgGAy3M4v2
* fix(templates): tidy the sidebar footer and add the edge rail
Space the footer like the menu above it: the shield aligned to the first
line, the slogan's two lines, then the name and version on their own
truncated lines in the body font. In icon mode only the shield remains,
with a tooltip carrying the same text.
Add shadcn's SidebarRail with a translated label and title, passed as
props that override the primitive's built-in "Toggle Sidebar".
Claude-Session: https://claude.ai/code/session_01KLvKwu4oUSHnFgGAy3M4v2
* refactor(ui-library): split auth-ui into presentational auth components
Replace the auth-ui block with four presentational registry components built
from shadcn primitives: auth-forms (Field, InputGroup, Alert), auth-methods
(Tabs, FieldSeparator, Button), auth-centered-layout and auth-split-layout.
They call no plugin and take every string as a prop with an English default.
The templates' sign-in, sign-up and password pages become application code
that wires the forms to the authentication plugin's headless actions,
translates them from client/locales, and keeps the NocoBase brand panel as
the split layout's aside. The ui-library preview loads shadcn/tailwind.css
and the shadcn Label so the data-attribute variants render.
Claude-Session: https://claude.ai/code/session_01KLvKwu4oUSHnFgGAy3M4v2
* fix(ui-library): keep auth demo links inside their demo
Claude-Session: https://claude.ai/code/session_01KLvKwu4oUSHnFgGAy3M4v2
* refactor(templates): install the auth registry blocks under client/extensions
Claude-Session: https://claude.ai/code/session_01KLvKwu4oUSHnFgGAy3M4v2
Moves every /api route in the repository onto the HTTP API specification: camelCase plugin namespaces, standard methods and slash-separated custom methods, { data } / { data, meta } responses, the standard error body with reason and domain, permission before validation, side-effect-free GETs, Repository errors that declare their own status, save-time validation of write grants, duplicate route detection at start, and optional global API limits in config.yml. All changed packages carry changesets.
* feat(hub-cli)!: deploy to remotes, save keys with hub auth, build for the Hub
hub-cli keeps the Apps an application deploys to as named remotes in the
committed .nocobase/hub.json (`hub remote add/list/remove`), saves one API
key per remote in the user's configuration directory (`hub auth
login/logout/status`), and no longer reads HUB_URL, HUB_APP_ID, HUB_API_KEY,
the App root .env or the --hub/--app-id/--api-key flags. Every command takes
--remote.
`hub deploy` and `hub upload` ask the Hub which platform its Host runs Apps
on and run `nocobase build --target … --node-version … --tar` for it before
uploading; --no-build and --file upload an existing archive after checking
its recorded target. `hub deploy` uploads and then deploys through the
deploy endpoint, so an archive the Hub already has is deployed as its
existing Release.
The Hub's upload route only uploads: the configuration-prefixed body and the
deployment-intent and wait headers are gone. Uploads are checked against the
Host's build target, the App detail reports it, and which routes a
publishing key may call is declared with each route. The Host reports its
runtime platform in its status.
* feat(hub-cli): add hub releases and hub status
`hub releases` lists an App's Releases newest first with the platform each
archive targets, whether it runs now and whether it ever deployed, and
`hub status` reports the platform the Hub builds for, what the App runs and
its last deployment. Finding the Release to roll back to no longer needs the
Hub's web page.
The Hub opens its Release list, single Release and deployment list to
publishing keys holding either scope. The Release list takes a `limit`, each
Release reports `buildTarget`, `running` and `everDeployed`, computed from
existing records, and deployment list items carry `finishedAt`.
* feat(hub-cli): upload archives resumably
hub-cli sends the archive through the Hub's resumable upload: a session for
the archive's size and checksum, chunks in order at the offset the Hub has
reached, then completion. A chunk whose answer is lost is resent from the
offset the Hub reports, a session left unfinished by an earlier run is
resumed, and an archive the Hub already has is not sent again. Archives may
be up to 2 GiB, and a reverse proxy only needs to allow one 8 MiB chunk.
The Hub stages sessions on local disk under a new `uploadsDir` option,
which the Hub template sets to storage/hub/uploads, expires them 24 hours
after their last chunk, and creates the Release on completion through the
same checks as the single upload, which the management console keeps using.
* fix(hub-cli): name the command to run when no remote is configured
* feat(app-cli): let a CLI plugin describe its nested topics
`defineCliPlugin` accepts `topics`, a one-line description for each topic
nested under the plugin's own. Help showed one of a nested topic's commands'
summaries in its place, so `hub remote` read "Add a Hub App to deploy this
application to." A topic is described only where a command under it is
registered, and a described topic with no command under it is rejected.
hub-cli describes `hub remote` and `hub auth`.
* fix(hub-cli): address review findings on remotes, retries and deadlines
- Stop create-app from ignoring .nocobase/ in a generated application's
.gitignore, so .nocobase/hub.json is committed as documented, and warn
from hub remote add when an existing checkout still ignores it.
- Count a failed offset read as one of the consecutive chunk failures
instead of ending the upload, and go on from the offset an
UPLOAD_OFFSET_MISMATCH reports without a second request.
- Give each Hub request its own deadline, report one that outlasts it as
TIMEOUT, and bound the wait for a deployment separately, so --timeout
no longer caps a whole resumable upload.
- Report a key as rejected in hub auth status only when the Hub rejects
it; anything else leaves it unchecked.
- Look remotes up as own properties, so a name like constructor is not a
remote, and reject a default that is not a remote name.
- Settle the hidden prompt when standard input ends or errors.
- Stage upload sessions one directory per App, scan only the App's own
sessions when an upload starts, and sweep every App's expired sessions
at most once an hour.
- Drop the unreachable not-found branch from getReleaseSummary.
* fix(hub-cli): roll back under the default key, name a missing Hub, cancel login cleanly
- `hub deploy --release-id` of a Release the App deployed before and has since
moved on from was answered with that earlier deployment, so the documented
rollback deployed nothing and exited 0. A reused deployment that is not the
App's latest now leads to the next key, derived from it; a retry walks the
same keys and still repeats nothing. A given --idempotency-key stays exact.
- A 404 without a Hub error code, as at a mistyped mount path, fails with
`HUB_NOT_FOUND` and suggests `hub remote list` instead of a bare
`HUB_REQUEST_FAILED` or an "unknown result".
- Ctrl-C at the `hub auth login` prompt reports `LOGIN_CANCELLED` (exit 130)
rather than `LOGIN_FAILED`.
* feat(queue): rebuild @nocobase/queue on BullMQ 6.3.6
Replace the @boringnode/queue wrapper with a per-application QueueService
whose producers, consumers and managers are bound to named queues. A
queueBackend of redis (or a registered BullMQ backend factory) runs on
BullMQ's public Queue and Worker APIs under a hash-tagged prefix; inMemory
runs in the process and persists unfinished jobs to a state file at
shutdown. Both implementations share one consumer layer and one contract
test suite.
- app-server: QueueServiceProvider, queueServiceToken and AppQueueConfig
replace QueueProvider and its tokens; the queue migration source and
planAppRuntimeDatabaseTasks are removed; queue.jobs is deprecated,
ignored and reported once per plugin
- templates: compose QueueServiceProvider, declare memory and redis keys,
drop the @/jobs alias
- create-plugin: remove the server.jobs capability
- examples: rewrite the queue example on the new API
- docs, Skills and AGENTS.md describe the new contract
* docs(jobs): make JobExecutor the default for background work
The previous commit rewrote every Queue Job reference onto the new queue
API, but most of what those jobs did belongs to @nocobase/jobs now.
- create-plugin: server.jobs generates a JobExecutor job and the provider
that owns the plugin's executor instead of being removed
- plugin and application development Skills: choose JobExecutor for
one-off work, ScheduleExecutor for recurring work, Scheduler when
administrators track it, and a queue only for delays, priorities,
deduplicating IDs, batches, rate limits and fan-out; jobs receive
services by closure
- Scheduler Skill, evals and docs: hand a target's lengthy work to a
JobExecutor with the occurrence's execution record as the reference,
and let the job decide its terminal outcome; describe Scheduler's own
jobs backend instead of the removed queue connection
- deployment and Notification Skills: cover the jobs and queue backends
instead of a queue manager
* refactor(queue): select the implementation with adapter
queueBackend used to pick both the implementation and a BullMQ backend
factory. A configuration now selects the implementation with
`adapter: 'inMemory' | 'redis'`, and the optional `queueBackend` only
names a factory registered with `registerBackend()` for the redis
adapter, defaulting to BullMQ's Redis backend. A registered factory
interprets its own connection, so `connection` is required only on the
Redis backend. `inMemory` is no longer a reserved factory name.
* docs(skills): route frontend work through an embedded shadcn/ui skill
The application development Skill now carries the shadcn/ui skill from
shadcn 4.21.0, unchanged, under references/frontend/shadcn/, and
references/frontend/references/shadcn.md says what to read there and
where an application departs from it: `pnpm exec shadcn`, no `apply` or
`--preset`, overlays as child routes, labels above inputs, and the
English built into a few primitives translated.
- Primitives are added on demand with `yes n | pnpm exec shadcn add`,
which keeps installed primitives from being overwritten and lets a
non-interactive run finish, then formatted with Prettier.
- styling.md, form.md and the other topic references link to the skill
instead of restating it; the worked example names the primitives each
file needs on an **Add first** line.
- The frontend handbook rework: the projects worked example split into
one document per file, shell.md, the capture tool guide and the
reviewer prompts.
- Both .prettierignore files skip the vendored skill so a shadcn upgrade
can replace it wholesale.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(app-template-default): ship only the primitives the shell uses
Primitives are added with the shadcn CLI when a page first needs one,
so every application, template and plugin starts from the same CLI
output. The shadcn/ui skill embedded in the development Skill replaces
the reference gallery.
- Remove client/pages/reference/ with its tests, the 49 primitives that
neither the shell nor the shipped compositions import, and
use-mobile.ts. The template keeps button, calendar, dialog,
dropdown-menu, input, label, popover, select, spinner, table, toast
and tooltip.
- Drop the devDependencies only those primitives used (recharts, cmdk,
embla-carousel-react, input-otp, react-resizable-panels,
@shadcn/react) and add cn, which registry primitives now import.
- toast.tsx names its close button through actions.close, as dialog.tsx
and spinner.tsx translate theirs; primitive-labels.test.tsx fails
when an update brings the registry's English back.
- DataTable takes showSelectedCount, so a table without row selection
hides "0 of N row(s) selected".
- Add the page test harness and application locale coverage tests; the
client routes test pins page grants by their authz resource id.
- AGENTS.md and CLAUDE.md send UI work to ui-workflow.md, list the
shipped primitives, and describe adding the rest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(templates): ship only the primitives Hub and Examples use
Hub and Examples follow Default: primitives are added with the shadcn
CLI when a page first needs one, and the shadcn/ui skill embedded in the
development Skill replaces the reference gallery.
- Remove client/pages/reference/ with its tests and use-mobile.ts from
both templates. Hub keeps the twelve primitives its shell and
compositions use; Examples also keeps badge, card, field, separator,
skeleton, textarea, toggle and toggle-group for its example pages.
- Drop recharts, cmdk, embla-carousel-react, input-otp,
react-resizable-panels and @shadcn/react, which no template imports
now, and add cn, which registry primitives import.
- Carry over Default's toast close label, DataTable showSelectedCount,
the page harness, locale coverage and primitive label tests, and the
AGENTS.md and CLAUDE.md guidance, keeping each template's own route
grants and wording.
- Add the changeset for all three templates.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(skills): name the primitives each template ships
The frontend handbook said the template ships twelve primitives, which
holds for Default and Hub but not for Examples. shadcn.md now lists the
eight Examples adds, and frontend-dev.md and example.md refer to the
primitives the shell uses instead of a count. Add the changeset for the
embedded shadcn/ui skill.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(skills): open records in place, add the back button and the dashboard template
A review of a customer-service application built from the handbook found records opening over the wrong page,
a row's Edit opening the drawer as well, a back button among the page actions, an unaligned table in a card and
unsortable date columns. The handbook now says a record opens over the page the user is on (I9), declares the
drawer under every page that opens it, gives a row's Edit its own route, puts BackButton above the title (L6),
makes date and number columns sortable (T1.8), and adds a dashboard template (T5) with a worked example.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(templates): add BackButton and keep the page count on one line
BackButton is the way back from a page below another one: a link above the heading that leads to the parent
route with the query string and replaces the history entry, as closing a route overlay does. It stands on its
own, without PageHeader. DataTablePagination gives the page count a minimum width, so the Chinese label no
longer wraps. RouteChildPage and the UI Library describe leaving by the back link instead of breadcrumbs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(skills): show the success path in the unsaved-changes example
A generated application hit this exact bug: the edit dialog's save
cleared neither the dirty flag that beforeClose reads nor the form's
report, so closing after a successful save asked to discard the just
saved changes.
The overlay.md section 2.5 example now carries the whole flow: a stable
onDirtyChange callback, an EditProjectBody whose onSubmitted clears the
flag before onSaved and close, and the imports that go with it. The
frontend handbook's Common mistakes list gains the matching entry.
* fix(templates): keep the Switch and pie chart in proportion in the compact theme
* docs(app-skills): compare the whole design at acceptance and require consistent navigation icons
The acceptance review's D classification was scoped to the design's numbered
criteria, so a design's structural declarations — routes, navigation entries and
their icons, permissions, the component list and states — were only compared
with the code when they happened to be criteria. A trial feature lost two menu
icons this way and the acceptance pass did not catch it.
D now compares the whole design file with the code; the design template requires
every declaration in sections 2–4 to map to a criterion or be marked explicitly
as not a criterion; and the review checklist plus page.md require navigation
icons to be consistent within a group.
* docs(app-skills): open a record's detail under the page that opens it
I9 covered drawers and dialogs only, so a page that referenced a record whose
detail is a page (a payment list's expense number) linked into the other
module's route: the page the user was on disappeared, the menu highlight moved,
and Back landed elsewhere. The page version of "the same drawer over another
page" was undocumented, and page.md told every record page to hard-code `to`,
which blocks reusing one page module under several parents.
I9 now covers a covering child page as well, child-routes.md gains "The same
detail page over another page", page.md limits `to` to a page with one parent,
and the common-mistakes entry names the detail page next to the overlay URL.
* fix(templates): make BackButton a muted text link
* refactor(templates): group the DataTable components in one directory
* docs(app-skills): show a cut-off table cell's full content on hover
Guideline T1.11 requires a table cell that is too narrow for its content to show the full content on hover. table.md gives the pattern: the cut-off content in a Popover whose trigger opens on hover, since a Tooltip does not work well here. A cell does not wrap and the table widens to fit it, so the pattern applies only where a column limits its width.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(app-skills): treat the worked example as a reference, not code to copy
Agents copied the projects example verbatim, carrying its names, fields and fixed values into features they did not fit. The frontend handbook now says the examples show the rules rather than the feature to build, and names the projects-domain values to decide again. example.md and styling.md no longer tell an agent to copy the files a task depends on; only session-expired-alert.tsx and use-url-search.ts, which are shared infrastructure, are still copied unchanged.
The acceptance review also checks the other direction of design conformance: names and copy keys from the projects domain, fields, columns, filters or actions the design does not declare, and example values that do not fit the feature's data are reported as D issues.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(app-skills): end a cut-off cell in an ellipsis and reveal it in a tooltip
A generated articles table clipped long titles mid-character and showed "release-notes" as "elease-note": the title used line-clamp in a cell that never wraps, and the tags put truncate on Badge, a flex element that shows no ellipsis and loses both ends of its centered text.
Guideline T1.11 now requires the ellipsis and a reveal on hover only when the content is cut off. table.md shows text and links, the name column included, in a Tooltip whose onOpenChange cancels it when the value fits; the tooltip trigger leaves a Link a link, which a Popover trigger would turn into a button. Styled content such as a Badge stays in a Popover, since a badge is unreadable on the inverted tooltip. It also says where truncate works and that line-clamp does not belong in a cell.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(templates): line DataTable up with a card by itself
A generated analytics page put a DataTable in a CardContent with px-0, as the handbook's "Table in a card" said, but not the cell padding that went with it. Its own border then sat on the card's edge, a strip was left below it, and the text started to the left of the card's title. The rule lived in four places and was still only half applied, because it asked the agent to pick a different component and hand-write selector classes.
DataTable now does it: inside a CardContent it drops its frame, reaches the card's edges and pads its first and last cells with --card-spacing, and a CardContent still given px-0 keeps working. The handbook builds a card's short list from DataTable with plain headers and no pagination, the dashboard example uses it, and guideline T1 says it covers list pages while a short list in a card follows T5.3, which is where the design had picked up sorting.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(app-skills): record every review checklist item in the review record
Both reviews of a generated content application were non-independent, since the environment could not start subagents, and neither checked T5.3: the design review raised only B1-B4 and S1-S4, and the acceptance review widened a clipped card without asking why the table sorted. The prompts already said to go through the checklist item by item, but the record kept only the items that failed, so a skipped item looked the same as a passed one.
The review record now has a "Review checklist" section with one row per checklist item: pass, fail with the issue it raised, or not applicable with the reason. Both prompts and the checklist's own introduction say to fill it in.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(app-skills): validate forms on submit, not as a field loses focus
A field error flashed for a frame whenever a dialog was closed without saving. Guideline T3.3 validated a field when it lost focus, so the handbook and its examples set useForm's mode to 'onTouched'; clicking Cancel, the close button or the backdrop takes the focus off the field first, and the error rendered while the dialog was fading out.
T3.3 now validates on submit, and a form closed without submitting shows no error. The handbook and the four examples leave mode at the default 'onSubmit', and it explains why the blur-based modes do not fit. After a failed submission a field is still revalidated as it changes, so its error clears once it is corrected.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(templates): let a child page inside another one cover it whole
A covering page under a tab of a record's page can only render through the tab's outlet, inside the record page's RouteChildPage. That layer both positioned and scrolled, so the nested layer resolved inset-0 against it and scrolled out of sight with its content: in the recruitment application, after the candidate page had been scrolled 292px, the offer page opened at top -240 and showed only its footer over the candidate's details.
RouteChildPage is now two elements, the way the layout's content area is: the outer one positions and never scrolls, the inner one scrolls, with overscroll-contain so scrolling stops at the layer. A layer rendered inside another one anchors to that layer's outer element and covers it whole. Inside another layer it also makes everything around it inert up to that layer's scrolling element — the record page's back link, header and tab bar — not only its own siblings. The layer carries data-slot='route-child-page'; the props are unchanged.
The three templates and the UI Library registry item carry the same file. The templates' AGENTS.md add that an overlay a page's header opens on a page with tabs is declared under every tab and linked through the current tab.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(app-skills): open a page header's overlays over the tab being shown
A review of the recruitment application found a record page whose header opened its edit dialog at /candidates/80/edit while the user was on /candidates/80/interviews. The handbook said a record opens over the page the user is on, but not that on a page with tabs that is the tab, and its two examples — the drawer with its stacked edit dialog, and the record page with tabs — never met. A link with a bare `edit` resolves against the route that renders it, not the URL on screen, and the header belongs to the page's route: the dialog replaced the tab in the page's outlet, and closing it went to the page's URL, which redirected to the default tab.
- Guidelines T2.1, I1, I6 and I9 define the view the user is on, the tab included, and I9 gives the test: an overlay's URL minus its own segments is the URL it was opened from, and closing returns there with no redirect.
- child-routes.md declares the header's overlays under every tab through customerHeaderRoutes(tab) inside customerDetailRoutes(owner), links the header through the tab read from the URL, and has each tab pass the page's context on to its outlet. page.md explains what a relative link resolves against, with a table of the cases.
- Going back restores the page underneath exactly (L6): links carry its whole query string down, a view below another one names its own parameters apart (table.md), and the way back removes them with withoutParams (example/url-search.md). child-routes.md no longer advises dropping the current page's filters when linking to another page's record, which lost them on the way back.
- example/detail-page-tabs.md is the complete page, a tab, a test that opens the header's "Edit" from every tab and goes back, and the route test helper; its code was compiled, linted and tested inside the default template.
- The review checklist, overlay.md, testing.md, frontend-dev.md and the run and design templates check overlays opened from a view other than the first one a page shows.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(templates): add DataTable and DatePicker from the UI Library on demand
The templates no longer ship DataTable or DatePicker, or the calendar,
select and table primitives only they used. Both are UI Library items
now, added with `shadcn add @nocobase/data-table` or
`@nocobase/date-picker` when a page first needs one. Examples keeps
select and table for its own pages, and Hub keeps react-day-picker,
which app-plugin-hub requires as a peer. The dataTable and datePicker
locale keys stay, so an item added later is translated at once.
- ui-library publishes data-table: DataTable and its column header,
pagination and view menu as one item of four files under
client/components/data-table/, with a preview demo and the
dropdown-menu, select and table primitives it renders with.
- date-time-picker declares the calendar, popover and react-day-picker
that the date-picker.tsx it installs imports; without calendar in the
templates, installing it alone no longer compiled.
- ui-library gets Vitest. The DataTable and DatePicker tests move there
from the templates and render the registry sources against the
preview's primitives; Quality runs them on every pull request and the
UI Library workflow before it publishes.
- The development Skill adds the items on the worked example's Add
first lines and says which of the CLI's package.json changes to undo;
the upgrade Skill covers an application that still has the old copies.
- The pending changesets that described a data-table directory in the
templates now describe what ships.
* refactor(templates): drop the unused Typography components
client/components/typography.tsx held the class strings from the shadcn
Typography guide for hand-written long-form text. Nothing in the
templates or the plugins imported it, and article content usually comes
from Markdown or rich text, which these components cannot style. The
templates' AGENTS.md and the development Skill no longer list it.
* feat(ui-library): publish BackButton and keep it preinstalled in the templates
Make the UI Library the source of truth for BackButton, as it already is
for PageHeader and the route overlays.
- ui-library: add the back-button component item (back-button.tsx, its
registry entry, a Navigation preview demo, and a test that renders it in
the strict runtime built from the components README), document it in the
components README with its navigation.back key, and use it in the
RouteChildPage demo instead of a hand-written back link.
- templates: keep client/components/back-button.tsx as an exact copy,
checked by tests/scripts/template-ui-library.test.mjs, and name
BackButton among the UI Library components in AGENTS.md. The component
itself is unchanged, and each template keeps its own back-button test,
which is the one check that the template's own locales carry the key.
- MAINTAINING.md and USAGE.md list back-button among the preinstalled
components, and MAINTAINING.md records navigation.back as the one
exception to item-prefixed keys: it predates the item and pairs with
the templates' navigation.breadcrumb.
- The development Skill's styling reference now says which composed
components are preinstalled from the UI Library and which are the
template's own, instead of saying the CLI cannot add any of them, and
the plugin Skill lists back-button among the items a plugin copies.
* feat(ui-library): add a ConfirmDialog item built on alert-dialog
ConfirmDialog confirms one action in an alert dialog the page opens from
its own state. It runs the action: while a returned promise is pending
the confirm button shows a spinner and holds the focus, both buttons are
disabled and Escape is ignored; resolving closes the dialog with
onOpenChange(false, 'confirm'), and a rejection or a returned
{ error, retryable } keeps it open with the error inside it. Cancel
holds the initial focus, and focusAfterConfirm names where focus goes
after a success, when the opener has often gone with its record.
A result is reported to the onOpenChange of the latest render, and one
that arrives after the caller closed or unmounted the dialog is dropped,
so a handler whose close meant cancel is not called with stale state.
A ref, not render state, keeps two clicks from running the action twice.
The preview gains the alert-dialog and spinner primitives, a demo with a
slow, a failing and a refused delete, and the item's tests render it in
the strict i18n runtime built from the README's Translations table.
* docs(app-skills): fix the frontend guidance the PR review found wrong
- The toast examples in complete-button.md and public-switch.md, and the
401 rule in api.md, used actionProps, left over from the Base UI toast
API; the toaster's option is action: { label, onClick }.
- ui-workflow.md's development step still said to copy the worked
example, as did frontend-dev.md and i18n.md in passing; they now say to
write the feature's files from its design and copy only what a
document calls shared infrastructure. i18n.md no longer lists the extra
shared keys twice with different wording.
- The customer page test in detail-page-tabs.md assumed a mocked i18n
client and queried keys; it renders in the strict test runtime with
the application's locale files and queries the wording. The document
also says detail/edit.tsx has to be written before the test imports it,
with the customers.form keys copy.md does not list, and no longer claims
the test checks what only the route test can.
- project-form.md and list-page.md name the select primitive they
import, and server-table.md says what it needs and names
data-table/index.tsx.
- The end-to-end guidance and the screenshot tool say what a Hub
application sets up first, since the Hub template has no Playwright.
- shadcn.md no longer claims the application installs CLI 4.21.0.
- The docs site's child page example leaves by BackButton, says why a
deeper outlet sits beside the layer as the component now behaves, and
its shadcn add example no longer offers to overwrite the translated
dialog primitive.
- form.md's create page is the frame to follow, not to copy.
* docs(app-skills): require RouteChildPage for a child route that is a page of its own
A generated application declared its article editor as a child route of a
dashboard and of a list and returned a bare PageContainer, so the editor
rendered at the parent's Outlet below the dashboard instead of covering it.
The handbook implied the rule without stating it.
- child-routes.md, page.md, form.md and frontend-dev.md state that only tab
content renders inline and a page of its own returns RouteChildPage,
including a form page shared by several parents.
- testing.md adds a covering child page test: the parent's heading sits in
an inert element, which fails for a page rendered inline.
- The template AGENTS.md files carry the rule, since they are always read.
- The UI Library README and the docs site place the parent's Outlet at the
end of its PageContainer, as the handbook does.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* docs: move deployment to its own chapter and make it agent-first
Move the deployment section out of the development chapter into a
top-level `deployment/` chapter in both languages, and rewrite it around
two routes: handing the deployment to an AI Agent, with the session
location, Skill and prompt for each scenario, and doing it by hand, with
one page each for Hub and standalone deployment. Runtime configuration
and backup/troubleshooting stay as trimmed reference pages.
Update the home page cards, top navigation, development index and the
tutorial's Hub placeholder to point at the new chapter, and fix the two
links into the old path in the default template README and the
app-installer Skill.
* docs: fix deployment guidance links and rollback
* docs: make agent deployment prompts actionable
* docs: group deployment sidebar entries
chenos