Five package-level test runners validating extension API contracts: - notes-runner: CRUD, folders, tags, search, backlinks (12 tests) - chat-runner: conversations, messaging, search (9 tests) - schedules-runner: CRUD + run (5 tests) - workflow-runner: definitions, instances, stage progression (5 tests) - renderer-runner: registry contract, block matching (4 tests) Runner Result API (in-memory, 3 admin endpoints) stores results from browser runs for CI consumption. Test-runners surface v0.2.0 posts results after each run and fixes suite prefix matching. CI integration via Playwright: wait-for-healthy.sh, run-surface-tests.sh, surface-test-driver.js. New test-runners stage in Gitea CI pipeline. Verified: 169 passed, 0 failed, 9 warned, 8 skipped on fresh install. Go handler tests: 4/4 passing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Packages
Installable .pkg archives for Chat Armature. Each subdirectory is a
package — either a surface (routable UI), an extension (hooks/tools/pipes),
or both (full type).
v0.28.7: Renamed from surfaces/. The .pkg format replaces .surface.
See docs/PACKAGES.md for the complete manifest schema and authoring guide. For workflow packages, see docs/WORKFLOW-PACKAGES.md.
Building
./packages/build.sh # build all → dist/*.pkg
./packages/build.sh icd-test-runner # build one
Installing
curl -X POST http://localhost:8080/api/v1/admin/packages/install \
-H "Authorization: Bearer $TOKEN" \
-F file=@dist/icd-test-runner.pkg
Or use the admin UI → System → Packages → Upload.
Archive Format
A .pkg file is a zip containing:
manifest.json — required (must have "id" and "title")
js/ — optional JavaScript assets
css/ — optional stylesheets
assets/ — optional images, icons, etc.
The manifest type field determines behavior:
surface(default) — routable page at/s/:slugextension— hooks, tools, and/or pipe filtersfull— both a surface and an extension
.surface archives are accepted as a backward-compatible alias.