Feat v0.6.3 dead code sweep (#38)

Co-authored-by: Jeffrey Smith <jasafpro@gmail.com>
Co-committed-by: Jeffrey Smith <jasafpro@gmail.com>

docs/DISTRIBUTION.md

@@ -21,20 +21,22 @@ The production Docker image ships with pre-built packages. A **curated default s
 | Package | Type | Description |
 |---------|------|-------------|
 | notes | surface | Markdown notes with graph view |
+| chat | surface | Real-time chat surface |
 | chat-core | library | Conversations, messages, read cursors |
-| workflow-chat | extension | Chat integration for workflow stages |
-| dashboard | surface | Dashboard surface |
-| workflow-demo | surface | Interactive walkthrough with diagrams |
-| bug-report-triage | workflow | Public entry, severity routing, SLA timers |
-| content-approval | workflow | Multi-party signoff example |
-| employee-onboarding | workflow | Automated provisioning + manager signoff |
+| mermaid-renderer | extension | Diagram rendering |
+| schedules | surface | Cron task management UI |
 
 #### Opt-in (ship in image, require `BUNDLED_PACKAGES` to enable)
 
 | Package | Type | Description |
 |---------|------|-------------|
 | tasks | full | Kanban/list task manager with webhooks |
-| schedules | surface | Cron task management UI |
+| workflow-chat | extension | Chat integration for workflow stages |
+| dashboard | surface | Dashboard surface |
+| workflow-demo | surface | Interactive walkthrough with diagrams |
+| bug-report-triage | workflow | Public entry, severity routing, SLA timers |
+| content-approval | workflow | Multi-party signoff example |
+| employee-onboarding | workflow | Automated provisioning + manager signoff |
 | editor | surface | Rich markdown editor |
 | hello-dashboard | surface | Welcome/getting started surface |
 | team-activity-log | surface | Team activity feed |
@@ -45,7 +47,6 @@ The production Docker image ships with pre-built packages. A **curated default s
 | gitea-client | library | Gitea API integration library |
 | js-sandbox | extension | JavaScript sandbox |
 | katex-renderer | extension | LaTeX rendering |
-| mermaid-renderer | extension | Diagram rendering |
 | regex-tester | extension | Regex testing tool |
 | icd-test-runner | surface | E2E API test suite |
 | sdk-test-runner | surface | SDK feature test suite |

docs/PACKAGE-REGISTRY.md

@@ -0,0 +1,94 @@
+# Package Registry
+
+The package registry lets admins browse and install packages from an external
+JSON index — a lightweight alternative to manually uploading `.pkg` files.
+
+## Registry JSON Format
+
+The registry is a static JSON file matching the `RegistryResponse` struct:
+
+```json
+{
+  "packages": [
+    {
+      "id": "notes",
+      "title": "Notes",
+      "version": "0.8.0",
+      "description": "Markdown notes with backlinks and graph view",
+      "author": "switchboard",
+      "type": "extension",
+      "tier": "core",
+      "download_url": "https://cdn.example.com/pkg/notes.pkg",
+      "size": 48200,
+      "updated_at": "2026-03-20T00:00:00Z"
+    }
+  ]
+}
+```
+
+### Required Fields
+
+| Field          | Description                                    |
+|----------------|------------------------------------------------|
+| `id`           | Package identifier (matches `manifest.json`)   |
+| `title`        | Display name                                   |
+| `version`      | Semver version string                          |
+| `description`  | Short description                              |
+| `download_url` | HTTPS URL to the `.pkg` file (must be HTTPS)   |
+
+### Optional Fields
+
+| Field        | Description                              |
+|--------------|------------------------------------------|
+| `author`     | Package author                           |
+| `type`       | `extension` or `library`                 |
+| `tier`       | `core`, `official`, or `community`       |
+| `size`       | File size in bytes                       |
+| `updated_at` | ISO 8601 timestamp of last update        |
+
+## Configuring the Registry URL
+
+### Via Admin UI
+
+Navigate to **Admin > Settings > Package Registry** and enter the registry URL.
+
+### Via API
+
+```bash
+curl -X PUT /api/v1/admin/settings/package_registry \
+  -H "Content-Type: application/json" \
+  -d '{"value": {"url": "https://cdn.example.com/pkg/registry.json"}}'
+```
+
+## Generating a Registry
+
+Use `scripts/generate-registry.sh` to build a `registry.json` from a
+directory of `.pkg` files:
+
+```bash
+# Default: reads dist/, uses placeholder base URL
+./scripts/generate-registry.sh
+
+# Custom directory and base URL
+./scripts/generate-registry.sh ./my-packages https://cdn.example.com/pkg > registry.json
+```
+
+Requirements: `jq`, `unzip`, and `stat` (GNU or BSD).
+
+## Self-Hosting
+
+Any HTTPS-capable file server works. Upload your `.pkg` files and the
+generated `registry.json` to the same directory, then point the admin
+setting to the `registry.json` URL.
+
+Example with a static file server:
+
+```
+/var/www/packages/
+  registry.json
+  notes.pkg
+  chat.pkg
+  chat-core.pkg
+```
+
+The registry is fetched and cached for 5 minutes on each browse request.