This repository has been archived on 2026-04-03. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
core/packages
Jeffrey Smith 0003e66e43
All checks were successful
CI/CD / detect-changes (pull_request) Successful in 3s
CI/CD / test-frontend (pull_request) Successful in 5s
CI/CD / test-go-pg (pull_request) Successful in 2m40s
CI/CD / test-sqlite (pull_request) Successful in 2m45s
CI/CD / build-and-deploy (pull_request) Successful in 25s
rebrand: sweep remaining switchboard refs + rename cookies/storage keys
- CSS headers (4 files): Switchboard Core → Armature
- Editor .mjs headers (8 files): Chat Switchboard → Armature
- SQL migration comments + seed data (20 files): Switchboard Core → Armature
- Webhook header: X-Switchboard-Event → X-Armature-Event
- Cookie: sb_token → arm_token (3 Go files + auth.js)
- localStorage: sb_auth → arm_auth (auth.js + 2 test runners)
- localStorage: switchboard_theme → armature_theme (theme.js + base.html)
- Debug engine filter: chatSwitchboard/switchboard/sb_ → armatureChat/armature/arm_
- JS export: switchboardTheme → armatureTheme (theme.mjs + code-editor.mjs)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-31 23:11:38 +00:00
..
2026-03-25 09:20:06 +00:00

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/:slug
  • extension — hooks, tools, and/or pipe filters
  • full — both a surface and an extension

.surface archives are accepted as a backward-compatible alias.