@cosmicdrift/kumiko-framework 0.412.0 → 0.413.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/agents/api/framework-engine.md +1 -0
- package/agents/boot-rules.md +343 -0
- package/agents/examples/api-docs.md +79 -71
- package/agents/examples/golden-path.md +11 -11
- package/agents/examples/{contact.md → helpdesk.md} +41 -34
- package/agents/examples.md +1 -1
- package/agents/features-index.md +2 -2
- package/agents/features.md +16 -16
- package/dist/engine/boot-validator/boot-report.d.ts +3 -0
- package/dist/engine/boot-validator/boot-report.js +2 -2
- package/dist/engine/boot-validator/boot-rules.d.ts +570 -0
- package/dist/engine/boot-validator/boot-rules.js +20 -0
- package/dist/engine/boot-validator/definition-config-events-jobs-rules.d.ts +77 -0
- package/dist/engine/boot-validator/definition-config-events-jobs-rules.js +77 -0
- package/dist/engine/boot-validator/definition-events-rules.d.ts +42 -0
- package/dist/engine/boot-validator/definition-events-rules.js +42 -0
- package/dist/engine/boot-validator/definition-feature-rules.d.ts +42 -0
- package/dist/engine/boot-validator/definition-feature-rules.js +42 -0
- package/dist/engine/boot-validator/definition-field-factories-rules.d.ts +17 -0
- package/dist/engine/boot-validator/definition-field-factories-rules.js +17 -0
- package/dist/engine/boot-validator/definition-handlers-rules.d.ts +72 -0
- package/dist/engine/boot-validator/definition-handlers-rules.js +72 -0
- package/dist/engine/boot-validator/definition-ownership-from-rules.d.ts +27 -0
- package/dist/engine/boot-validator/definition-ownership-from-rules.js +27 -0
- package/dist/engine/boot-validator/definition-probes-rules.d.ts +47 -0
- package/dist/engine/boot-validator/definition-probes-rules.js +47 -0
- package/dist/engine/boot-validator/definition-role-assignment-rules.d.ts +27 -0
- package/dist/engine/boot-validator/definition-role-assignment-rules.js +27 -0
- package/dist/engine/boot-validator/definition-ui-extensions-rules.d.ts +197 -0
- package/dist/engine/boot-validator/definition-ui-extensions-rules.js +197 -0
- package/dist/engine/boot-validator/definition-webhook-events-rules.d.ts +32 -0
- package/dist/engine/boot-validator/definition-webhook-events-rules.js +32 -0
- package/dist/engine/define-feature.js +26 -9
- package/dist/engine/define-handler.js +8 -4
- package/dist/engine/definition-violations.d.ts +14 -0
- package/dist/engine/definition-violations.js +71 -0
- package/dist/engine/entity-handlers.js +39 -13
- package/dist/engine/event-def.js +32 -12
- package/dist/engine/factories.js +16 -5
- package/dist/engine/feature-config-events-jobs.js +63 -27
- package/dist/engine/feature-entity-handlers.js +15 -6
- package/dist/engine/feature-probes.js +29 -9
- package/dist/engine/feature-ui-extensions.js +178 -92
- package/dist/engine/object-form.js +8 -2
- package/dist/engine/ownership.js +17 -5
- package/dist/engine/registry-validate.d.ts +1 -0
- package/dist/engine/registry-validate.js +7 -0
- package/dist/engine/registry.js +2 -1
- package/dist/engine/role-assignment.js +17 -5
- package/dist/engine/soft-delete-cleanup.js +4 -3
- package/dist/engine/webhook-events.js +20 -6
- package/dist/files/feature.js +1 -0
- package/dist/files/file-routes.js +1 -1
- package/dist/jobs/job-runner-gates.js +5 -1
- package/dist/schema-cli/shared.d.ts +11 -0
- package/dist/schema-cli/shared.js +37 -3
- package/dist/schema-cli/validate-command.js +10 -3
- package/package.json +3 -3
- package/src/changes.json +12 -0
package/agents/features-index.md
CHANGED
|
@@ -48,8 +48,6 @@ One entry per feature a package ships: purpose, import of its factory, required
|
|
|
48
48
|
`import { createComplianceProfilesOpsFeature } from "@cosmicdrift/kumiko-bundled-features/compliance-profiles-ops"`; requires `compliance-profiles`, `tenant`
|
|
49
49
|
- `config`: Stores per-tenant (and optionally per-user) configuration values with a multi-layer cascade: user-row → tenant-row → system-row → app-override (deploy-time `AppConfigOverrides`) → computed → feature default.
|
|
50
50
|
`import { createConfigFeature } from "@cosmicdrift/kumiko-bundled-features/config"`
|
|
51
|
-
- `contact`: Contact inbox: an anonymous browser client (GET /contact/client.js) submits questions, contact requests, bug reports and wishes behind a honeypot, a minimum submit time and a single-use proof-of-work challenge; signed-in users file reports from the admin.
|
|
52
|
-
`import { createContactFeature } from "@cosmicdrift/kumiko-bundled-features/contact"`; requires `config`, `delivery`, `user-data-rights`, `files`, `notes-history`
|
|
53
51
|
- `crypto-shredding`: Operator-level crypto-shredding trigger.
|
|
54
52
|
`import { createCryptoShreddingFeature } from "@cosmicdrift/kumiko-bundled-features/crypto-shredding"`
|
|
55
53
|
- `custom-fields`: Tenant- and system-scoped custom field definitions with generic value storage on any host entity.
|
|
@@ -90,6 +88,8 @@ One entry per feature a package ships: purpose, import of its factory, required
|
|
|
90
88
|
`import { createFormDraftFeature } from "@cosmicdrift/kumiko-bundled-features/form-draft"`
|
|
91
89
|
- `form-draft-user-data`: GDPR (Art.
|
|
92
90
|
`import { createFormDraftUserDataFeature } from "@cosmicdrift/kumiko-bundled-features/form-draft-user-data"`; requires `user-data-rights`
|
|
91
|
+
- `helpdesk`: Helpdesk inbox: an anonymous browser client (GET /helpdesk/client.js) submits questions, contact requests, bug reports and wishes behind a honeypot, a minimum submit time and a single-use proof-of-work challenge; signed-in users file reports from the admin.
|
|
92
|
+
`import { createHelpdeskFeature } from "@cosmicdrift/kumiko-bundled-features/helpdesk"`; requires `config`, `delivery`, `user-data-rights`, `files`, `notes-history`
|
|
93
93
|
- `host-routing`: Host- and path-based tenant routing: an authoritative tenant resolver from the subdomain (tenantBy host), a tenant existence check against enabled, active tenants, and the tenant-key query behind createHostDispatch, which picks the HTML file, CSP, locale redirect or 404 per host for runProdApp's hostDispatch.
|
|
94
94
|
`import { createHostRoutingFeature } from "@cosmicdrift/kumiko-bundled-features/host-routing"`; requires `auth-foundation`, `tenant`
|
|
95
95
|
- `inbound-mail-foundation`: Plugin host for inbound e-mail (inbox federation) — provider plugins (inbound-provider-imap, later M365 Graph / Gmail REST) register at the `inboundMailProvider` extension point with verify/fetch and optional oauth/watch (live push) and send.
|
package/agents/features.md
CHANGED
|
@@ -194,22 +194,6 @@ Stores per-tenant (and optionally per-user) configuration values with a multi-la
|
|
|
194
194
|
|
|
195
195
|
Category: infrastructure
|
|
196
196
|
|
|
197
|
-
## contact
|
|
198
|
-
|
|
199
|
-
Contact inbox: an anonymous browser client (GET /contact/client.js) submits questions, contact requests, bug reports and wishes behind a honeypot, a minimum submit time and a single-use proof-of-work challenge; signed-in users file reports from the admin. Every request is stored platform-wide and every SystemAdmin is notified by mail, optionally also in a Telegram chat (option `telegram`, off by default); the notification names only the kind, the app and a link, never name, address, phone, subject or message, because mail and Telegram cannot be shredded. SystemAdmins reply by mail (Reply-To set, attachments, quoting the original) and mark requests done; a website sender gets a fixed acknowledgement, a signed-in reporter a copy and an in-app note. Personal data is crypto-shredding-ready and the EXT_USER_DATA hooks export and erase a user's requests.
|
|
200
|
-
|
|
201
|
-
Category: communication
|
|
202
|
-
|
|
203
|
-
Requires: `config`, `delivery`, `user-data-rights`, `files`, `notes-history`
|
|
204
|
-
|
|
205
|
-
Optional requires: `channel-telegram`
|
|
206
|
-
|
|
207
|
-
Config keys:
|
|
208
|
-
|
|
209
|
-
| Key | Type | Scope | Default |
|
|
210
|
-
| --- | --- | --- | --- |
|
|
211
|
-
| `reply-to` | text | system | `` |
|
|
212
|
-
|
|
213
197
|
## crypto-shredding
|
|
214
198
|
|
|
215
199
|
Operator-level crypto-shredding trigger. `forget-subject` erases a user or tenant subject key in the configured KMS adapter, making every PII field encrypted under it permanently unreadable (reads render the `[[erased]]` sentinel), and appends a `subject-forgotten` audit event. Requires a KMS adapter (`runProdApp({ kms })`). The automated Art.-17 deletion pipeline in `user-data-rights` erases keys itself; this command covers manual forgets (authority requests, operator recovery, tenant destroy).
|
|
@@ -397,6 +381,22 @@ Requires: `user-data-rights`
|
|
|
397
381
|
|
|
398
382
|
Optional requires: `form-draft`
|
|
399
383
|
|
|
384
|
+
## helpdesk
|
|
385
|
+
|
|
386
|
+
Helpdesk inbox: an anonymous browser client (GET /helpdesk/client.js) submits questions, contact requests, bug reports and wishes behind a honeypot, a minimum submit time and a single-use proof-of-work challenge; signed-in users file reports from the admin. Every request is stored platform-wide and every SystemAdmin is notified by mail, optionally also in a Telegram chat (option `telegram`, off by default); the notification names only the kind, the app and a link, never name, address, phone, subject or message, because mail and Telegram cannot be shredded. SystemAdmins reply by mail (Reply-To set, attachments, quoting the original) and mark requests done; a website sender gets a fixed acknowledgement, a signed-in reporter a copy and an in-app note. Personal data is crypto-shredding-ready and the EXT_USER_DATA hooks export and erase a user's requests.
|
|
387
|
+
|
|
388
|
+
Category: communication
|
|
389
|
+
|
|
390
|
+
Requires: `config`, `delivery`, `user-data-rights`, `files`, `notes-history`
|
|
391
|
+
|
|
392
|
+
Optional requires: `channel-telegram`
|
|
393
|
+
|
|
394
|
+
Config keys:
|
|
395
|
+
|
|
396
|
+
| Key | Type | Scope | Default |
|
|
397
|
+
| --- | --- | --- | --- |
|
|
398
|
+
| `reply-to` | text | system | `` |
|
|
399
|
+
|
|
400
400
|
## host-routing
|
|
401
401
|
|
|
402
402
|
Host- and path-based tenant routing: an authoritative tenant resolver from the subdomain (tenantBy host), a tenant existence check against enabled, active tenants, and the tenant-key query behind createHostDispatch, which picks the HTML file, CSP, locale redirect or 404 per host for runProdApp's hostDispatch.
|
|
@@ -1,3 +1,6 @@
|
|
|
1
|
+
import { type BootViolation } from "./boot-rule.ts";
|
|
2
|
+
export declare function isRuntimeCrash(thrown: unknown): boolean;
|
|
3
|
+
export declare function violationsOf(failure: Error, checkName: string, feature: string | undefined): readonly BootViolation[];
|
|
1
4
|
export type BootReport = {
|
|
2
5
|
check(checkName: string, feature: string | undefined, fn: () => unknown): boolean;
|
|
3
6
|
endPhase(): void;
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
import { BootRuleFailures, BootRuleViolation, BootValidationError, } from "./boot-rule.js";
|
|
2
2
|
// A runtime crash is a bug in a validator (or in the input it assumed), not a
|
|
3
3
|
// rule violation: it must surface as itself instead of masquerading as a finding.
|
|
4
|
-
function isRuntimeCrash(thrown) {
|
|
4
|
+
export function isRuntimeCrash(thrown) {
|
|
5
5
|
return (!(thrown instanceof Error) ||
|
|
6
6
|
thrown instanceof TypeError ||
|
|
7
7
|
thrown instanceof RangeError ||
|
|
@@ -10,7 +10,7 @@ function isRuntimeCrash(thrown) {
|
|
|
10
10
|
thrown instanceof EvalError ||
|
|
11
11
|
thrown instanceof URIError);
|
|
12
12
|
}
|
|
13
|
-
function violationsOf(failure, checkName, feature) {
|
|
13
|
+
export function violationsOf(failure, checkName, feature) {
|
|
14
14
|
if (failure instanceof BootRuleFailures) {
|
|
15
15
|
return failure.failures.flatMap((nested) => violationsOf(nested, checkName, feature));
|
|
16
16
|
}
|