Zayin/Ekklesia
3
0
Fork 0
Code Issues 6 Pull Requests 1 Actions Packages Projects Releases 9 Wiki Activity

Add the module navigation contract: manifest v9, module routes, return-to-origin

Browse Source 
Stage 1 PR 7 (ADR 0063). A module becomes a first-class part of the Dashboard.

- Manifest v9 = v8 plus optional `navigation`: a Lucide icon from the curated
  MODULE_NAVIGATION_ICONS set, and up to 12 primary pages (stable id, safe
  label, kebab-case path relative to the module root; no traversal, schemes,
  queries, duplicates, or nesting). Validated before activation.
- Version 8 stays accepted beside version 9, each read strictly as itself
  (discriminated union); no released manifest is rewritten. The template
  moves to v9; the released Signage 0.1.5 manifest is a test fixture.
- Real module routes: /<id> is the landing view, /<id>/<page> a declared
  page, anything beneath a page a module-owned detail route; anything else
  is not-found and mounts nothing. api/assets/display are never pages.
- Sidebar: declared icons, pages nested under an open module, one
  aria-current, collapsed and drawer behaviour; v8 modules unchanged.
- module-ui-sdk: ModuleUiHostContext.navigation (location, subscribe,
  navigate, link, settings), refusing anything outside the module's routes;
  undefined on the display host. Mount ABI unchanged.
- Return-to-origin: one `?return=` carrier on Settings URLs, validated by
  parseReturnTarget and against running modules' declared routes; Settings
  Back returns to exactly the originating module page, across refreshes.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
ekklesia
2026-10-15 08:21:50 -05:00
co-authored by Claude Opus 5.5
parent 7447381c8f
commit 4671622b9d
69 changed files with 4221 additions and 372 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture/platform-architecture.md
+11 -1
View File
@@ -614,7 +614,17 @@ Core one typed column per preference and served only to their owner (`GET /api/v
`PATCH /api/v1/account/preferences`, `core.account.self.manage`), so they follow the person to every
device. A small same-origin script in the page's `<head>` applies this browser's cached copy before
first paint, and the account's answer replaces it on every load
([ADR 0062](decisions/0062-account-area-and-synced-appearance-preferences.md)). `pnpm boundaries` opens
([ADR 0062](decisions/0062-account-area-and-synced-appearance-preferences.md)). A module is a
first-class application area. Manifest version 9 declares its Lucide icon, from a curated set the
Dashboard imports by name, and its primary pages. The sidebar nests those pages beneath it while it is
open. Routes go to the module's root, to a declared page, or to anything beneath a page; anything
else under a module is not-found and mounts nothing. The host's `api`, `assets`, and `display`
namespaces are never pages. The mounted module receives `context.navigation`, a narrow capability to
read its location, move among its own routes, make real links, and open its Settings page. The
Settings URL carries `?return=` with where the module was; it is validated against the running
modules and their declared routes, and Back returns there. Manifest version 8 stays accepted beside
version 9, read strictly as itself
([ADR 0063](decisions/0063-module-navigation-contract-manifest-v9.md)). `pnpm boundaries` opens
exactly two shared roles to modules **by name**, and pins both design packages beneath everything
else. The Dashboard and display install the defaults at their document root; custom properties
inherit into every module artifact, so a module reads `var(--ekklesia-…)` with nothing to import at