Jeffrey Smith
f1c47002aa
All checks were successful
CI/CD / detect-changes (pull_request) Successful in 23s
CI/CD / test-frontend (pull_request) Successful in 26s
CI/CD / test-go-pg (pull_request) Successful in 2m35s
CI/CD / test-sqlite (pull_request) Successful in 3m19s
CI/CD / build-and-deploy (pull_request) Successful in 1m46s
sw.testing SDK module — structured test framework for surface runners: - suite/test registration, lifecycle hooks (beforeAll/afterAll/beforeEach/afterEach) - Assertion library (ok/eq/neq/gt/match/throws/status/shape/arrayOf) - Auto-cleanup via track(type, id) with LIFO deletion - Three result statuses: passed/failed/warned - Structured JSON results with timing, warnings, cleanup stats test-runner manifest type: - ValidateManifest accepts "test-runner" packages - Excluded from sidebar nav (extensionNavItems filters surface/full only) - DB migrations: SQLite 013, Postgres 014 (CHECK constraint) ICD runner migration (kernel-only): - Migrated from T.test()/T.assert() to sw.testing.suite() - Stripped extension-dependent tests (channels, notes, personas, etc.) - Kernel suites: smoke, crud, authz, security, providers, packaging, sdk - Deleted ui.js + css (rendering delegated to registry surface) SDK runner migration (kernel-only): - Migrated from T.dualTest()/T.domains to sw.testing.suite() - Stripped extension domains (belong in v0.7.2 package runners) - Kernel suites: misc, workflows, admin, packages, connections, deps, composition Runner registry surface (/s/test-runners): - Admin-only dashboard discovering test-runner packages - Run All / per-runner Run buttons, real-time results - Export Failures / Export Full Results (JSON download) - Dark mode styling using kernel CSS variables - Suite count polling for async runner script loading 141 passed, 0 failed on fresh minimal install. 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.