@open-matrix/conformance-harness (0.1.26)
Installation
@open-matrix:registry=npm install @open-matrix/conformance-harness@0.1.26"@open-matrix/conformance-harness": "0.1.26"About this package
Conformance harness
This published library turns four developer proof rituals into maintained,
typed checks. @open-matrix/hive-pm exposes the supported command-line surface;
each command writes one JSON report and exits nonzero when any assertion fails.
Run from the repository root through the root package scripts:
pnpm prove:manifest -- --target ../../applications/chat/ui
pnpm prove:package-install -- \
--deployment <deployment-root> \
--target component-store://<package-name>@<package-version> \
--package-name <package-name> \
--package-version <package-version> \
--matrix-home <mode-0600-matrix-home> \
--control-root <selected-hivedock-authority-root> \
--control-mount workspaces.<binding>.hivedock.control \
--target-host-id <selected-hivedock-id>
pnpm prove:application -- \
--package-name <package-name> \
--package-version <package-version> \
--application <application-name> \
--component-tag <custom-element-tag> \
--ready-text <visible-ready-text> \
--standalone-page <standalone-application-url> \
--matrix-credential-file <mode-0600-matrix-credential-file> \
--authority-root <selected-hivedock-authority-root> \
--shell-page <normal-shell-url>
pnpm prove:credential-boundary -- \
--credential-file <mode-0600-delegated-credential-file> \
--outside-root <another-tenant-root>
prove:package-install uses an authenticated package-control package.up
message path and then requires both a canonical durable install record and every
declared runtime to be running. A delegated developer supplies a Matrix home
whose transport root is the granted tenant.workspaces.<binding> subtree,
qualifies the attenuated control mount with the selected HiveDock authority
root, and supplies the selected HiveDock identity. The rooted Matrix address
uses broker-native replies across the transport-root boundary without widening
the credential. An operator may omit all three control options to use the local
authority-root hivedock.control. It never starts a second bare supervisor.
prove:application supports either canonical browser login
(--credential-file plus --principal) or a selected disposable HiveDock's
direct Matrix credential (--matrix-credential-file, --authority-root, and
--shell-page). The latter substitutes only authenticated browser bootstrap;
Directory, Registry, Matrix requests, digest verification, module import, and
application execution remain live. The check proves lazy loading, a
component.module.get browser frame, absence of HTTP compatibility artifacts,
detached SubjectViewBindingV1 delivery with the installed logical subject,
DOM connection, and visible useful readiness.
When --standalone-page is supplied, the same authenticated browser context
also opens that exact /apps/<app>/ URL. The proof requires a successful HTML
document, no redirect to a shell alias, the declared custom element connected,
the same useful-ready text visible, and a clean standalone console. This second
phase does not weaken the installed-shell phase's ban on HTTP artifact loading.
prove:credential-boundary proves an inside-subtree publish/subscribe round
trip and loud refusal of both publish and subscribe outside that subtree.
Credentials are supplied only by mode-0600 file paths; never put credential
values on the command line.
Dependencies
Dependencies
| ID | Version |
|---|---|
| @open-matrix/contracts | 0.1.23 |
| @open-matrix/core | 0.1.29 |
| @open-matrix/package-artifacts | 0.1.26 |
| @open-matrix/package-runtime | 0.1.33 |
| @playwright/test | ^1.57.0 |
| nats | ^2.29.3 |
Development Dependencies
| ID | Version |
|---|---|
| @types/node | ^20.0.0 |
| tsx | ^4.21.0 |
| typescript | ^5.7.0 |