26 lines
1.6 KiB
Markdown
26 lines
1.6 KiB
Markdown
# Project creation in administration — 14 October 2026
|
||||
|
|
|
|||
|
|
The administrator UI now includes a Projects section, existing project summaries,
|
|||
|
|
and a creation form using the established `/v1/admin/projects` API. It collects a
|
|||
|
|
name, stable project slug, owner ID, purpose and 1–30 research questions. Owner
|
|||
|
|
identity defaults to `/v1/me`. Creation refreshes project options for account and
|
|||
|
|
credential grants without reloading the page. Failures preserve the form for retry.
|
|||
|
|
|
|||
|
|
The default initial policy explicitly permits source registration and supported
|
|||
|
|
research record types that pass service validation. The checkbox explains this and
|
|||
|
|
can require review instead. Protected intent/policy/deletion/merge changes retain
|
|||
|
|
owner authorization. Cross-project includes start empty. No project is created on
|
|||
|
|
the operator's behalf; the operator fills in the form and submits it.
|
|||
|
|
|
|||
|
|
PASS: TypeScript, ESLint, 20 frontend tests and production build; existing project
|
|||
|
|
administration API test; deployed admin page HTTP 200. The new integrated UI test
|
|||
|
|
covers identity defaults, slug generation, policy and CSRF payload, server conflict
|
|||
|
|
preserving inputs, successful creation, and updated account/key grant selectors.
|
|||
|
|
|
|||
|
|
LIMITED: shared preview status/open calls timed out. Rendered screenshot, keyboard
|
|||
|
|
and responsive browser checks could not be completed during this change. Existing
|
|||
|
|
styles and semantic form controls are reused; no accessibility audit is claimed.
|
|||
|
|
|
|||
|
|
The working tree already contained uncommitted application work. Changes were kept
|
|||
|
|
in the admin UI, tests, CSS and setup documentation; no commit or knowledge mutation
|
|||
|
|
was performed.
|