ekklesiaandClaude Opus 5.5
89ef4b5ff6
CI / verify (pull_request) Successful in 1m12s
CI / infrastructure-smoke (pull_request) Successful in 37s
CI / package-release (pull_request) Successful in 51s
CI / migration-smoke (pull_request) Successful in 2m29s
CI / image-build (pull_request) Successful in 1m4s
CI / deploy-smoke (same-origin) (pull_request) Successful in 54s
CI / package-publication (pull_request) Successful in 58s
CI / deploy-smoke (split) (pull_request) Successful in 2m56s
The Settings foundation (ADR 0061):
- URL model. /settings is a real landing page. The platform sections
are /settings/general, /branding, /displays, and /system. Module
lifecycle is Discover: /settings/discover/browse, /installed, and
/updates. /settings/discover is respelled in place to Browse's one
canonical address. A module's settings are /settings/<module-id>,
never nested under Discover. Deeper Settings addresses are
reserved. "Modules" stays the user-facing word: "Discover modules",
"Installed modules", "Module updates".
- Collisions. Core's one reserved list gains the Settings section
names (branding, discover, displays, general, system) as a second
documented group, so no module id can shadow a section; `modules` is
an ordinary id. apps/api tests hold it equal to the shell's sections.
- Navigation. One Settings item in the same sidebar expands in place
into Platform and Modules (and Discover's three views) while in
Settings, and the phone drawer has the same hierarchy. The rest of
the navigation stays.
- Permissions. GET /api/v1/dashboard/settings evaluates, through
Core's evaluator, which destinations the viewer may see:
- Displays: core.devices.manage
- Discover: core.modules.lifecycle.manage
- a module's settings: core.modules.configuration.manage, for each
module that declares configuration (ADR 0029)
- General, Branding, System: the platform owner, until each has its
own permission
These are presentation hints; every data route keeps its own
enforcement. With nothing visible, there is no Settings link.
- Pages are honest placeholders with Back to Settings. A disabled
module's settings say it is turned off; a section or module the
person cannot see says so without detail; an unknown name is not
found; a failed load withholds the link and offers Retry.
- The deploy smoke opens Settings by deep link, refreshes a section,
enters Discover, opens the module's settings, uses the phone
drawer, and returns to the Dashboard.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
54 lines
1.7 KiB
TypeScript
54 lines
1.7 KiB
TypeScript
/**
|
|
* The framework-free half of the Ekklesia shell: how it talks to the platform and how it builds a
|
|
* module UI host context. Deliberately the only public surface of this package.
|
|
*
|
|
* The React shell itself (`src/browser/`) is not exported. It is an application, bundled straight to
|
|
* a browser artifact by this package's own build; exporting components would invite another package
|
|
* to depend on Ekklesia's shell internals, which is exactly the coupling the surface boundary
|
|
* exists to prevent. What *is* exported is the protocol — validated wire parsing, context
|
|
* construction, module API resolution — so the end-to-end test can drive the real host code against
|
|
* a real server instead of a reimplementation of it.
|
|
*/
|
|
export {
|
|
bootstrapHost,
|
|
bootstrapDisplayHost,
|
|
type DashboardNavigation,
|
|
type DashboardSettings,
|
|
type DashboardSettingsModule,
|
|
type DashboardNavigationEntry,
|
|
type DashboardNavigationGroup,
|
|
type DisplayHostBootstrap,
|
|
type EkklesiaHostConfig,
|
|
type HostBootstrap,
|
|
type HostEventSourceFactory,
|
|
type HostEventSourceOptions,
|
|
type HostModuleDisplayResponse,
|
|
type HostModuleUiDescriptor,
|
|
HostProtocolError,
|
|
type HostProtocolErrorCode,
|
|
loadDashboardNavigation,
|
|
loadDashboardSettings,
|
|
loadHostPrincipal,
|
|
loadModuleDisplay,
|
|
moduleDisplayDescriptorPath,
|
|
parseDashboardNavigation,
|
|
parseDashboardSettings,
|
|
parseDisplayRoute,
|
|
parseHostModuleDisplay,
|
|
parseHostPrincipal,
|
|
resolveApiOrigin,
|
|
resolveApiUrl,
|
|
} from "./host-protocol.js";
|
|
export {
|
|
type CreateModuleUiContextOptions,
|
|
createModuleUiContext,
|
|
moduleUiSourceUrl,
|
|
} from "./module-context.js";
|
|
export {
|
|
HostAuthError,
|
|
type HostAuthErrorCode,
|
|
type HostSignInCredentials,
|
|
signInWithEmail,
|
|
signOutHost,
|
|
} from "./auth-protocol.js";
|