@cynodia/axiom-server 0.8.0-alpha.1 → 0.8.2-alpha.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/README.md +7 -1
- package/conformance/authenticated-client-rejects-system-only-action.json +702 -0
- package/conformance/effect-retry-sequence.json +714 -0
- package/conformance/effect-success-event.json +703 -0
- package/conformance/event-payload-invalid.json +696 -0
- package/conformance/failed-effect-structured-outcome.json +704 -0
- package/conformance/integration-query-success.json +704 -0
- package/conformance/integration-query-timeout.json +706 -0
- package/conformance/late-query-rejection-after-timeout.json +129 -0
- package/conformance/late-query-result-after-timeout.json +127 -0
- package/conformance/manifest.json +226 -4
- package/conformance/rolled-back-action-produces-no-effect.json +723 -0
- package/conformance/simultaneous-same-instant-triggers-both-commit.json +690 -0
- package/conformance/system-only-action-rejects-client.json +698 -0
- package/conformance/timed-trigger-polling.json +699 -0
- package/conformance/verified-external-event-invokes-system-only-action.json +695 -0
- package/dist/conformance-runner.d.ts +11 -0
- package/dist/conformance-runner.js +216 -0
- package/dist/conformance-types.d.ts +105 -0
- package/dist/conformance-types.js +1 -0
- package/dist/effects.d.ts +8 -0
- package/dist/effects.js +2 -1
- package/dist/index.d.ts +1 -0
- package/dist/index.js +1 -0
- package/dist/integration.d.ts +6 -2
- package/dist/integration.js +4 -4
- package/dist/node-host.d.ts +15 -0
- package/dist/node-host.js +10 -3
- package/dist/server.d.ts +7 -0
- package/dist/server.js +102 -8
- package/dist/triggers.d.ts +19 -0
- package/dist/triggers.js +9 -2
- package/package.json +3 -3
- package/schema/protocol.v1.schema.json +1 -1
- package/schema/server-ir.v1.schema.json +1 -1
- package/schema/server-ir.v2.schema.json +16 -1
- package/schema/server-ir.v3.schema.json +16 -1
- package/schema/server-ir.v4.schema.json +1819 -0
package/README.md
CHANGED
|
@@ -31,7 +31,8 @@ Main exports: `createAxiomServer`, `createMemoryPersistence`, `createSqlitePersi
|
|
|
31
31
|
`createServerHost`, `createDeterministicServerHost`, `createDirectTransport`,
|
|
32
32
|
`createHttpTransport`, `createRemoteGateway`, `serveOverHttp`, `serveAxiomApplication`,
|
|
33
33
|
`createFakeIntegrationAdapter`, `createHttpIntegrationAdapter`, `createTriggerRuntime`,
|
|
34
|
-
`createEffectRunner`, `
|
|
34
|
+
`createEffectRunner`, `runConformanceFixture`, `runConformanceSuite`,
|
|
35
|
+
`SERVER_DIAGNOSTIC_CODES`.
|
|
35
36
|
|
|
36
37
|
`serveAxiomApplication` is the whole deployment story: it serves the generated page at `GET /`
|
|
37
38
|
and the semantic endpoint at `POST /axiom`, from one process, for any Axiom application. No
|
|
@@ -48,11 +49,16 @@ implementation in another language needs to conform to it:
|
|
|
48
49
|
@cynodia/axiom-server/schema/server-ir.v1.schema.json JSON Schema for the frozen v1 IR
|
|
49
50
|
@cynodia/axiom-server/schema/server-ir.v2.schema.json JSON Schema for v2 (+ group, expression-ref)
|
|
50
51
|
@cynodia/axiom-server/schema/server-ir.v3.schema.json JSON Schema for v3 (+ integrations, effects, triggers, events)
|
|
52
|
+
@cynodia/axiom-server/schema/server-ir.v4.schema.json JSON Schema for v4 (+ invocation source, structured effect outcome)
|
|
51
53
|
@cynodia/axiom-server/schema/protocol.v1.schema.json JSON Schema for the protocol
|
|
52
54
|
```
|
|
53
55
|
|
|
54
56
|
The fixtures are pure data. Running them requires no part of this implementation — which is
|
|
55
57
|
the point: the semantic contract, the schemas and these files are the whole specification.
|
|
58
|
+
`runConformanceFixture`/`runConformanceSuite` are a public TypeScript reference runner over
|
|
59
|
+
that fixture format, for this implementation's own use or a consumer building against it;
|
|
60
|
+
the fixture *model* they accept is deliberately independent of them, so a non-TypeScript
|
|
61
|
+
implementation needs only the shapes and the semantics documented in `docs/AUTHORITY.md`.
|
|
56
62
|
|
|
57
63
|
## Installation
|
|
58
64
|
|