runcastle 1.6.0 → 1.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -22,20 +22,19 @@ self-contained package under `build/`:
22
22
 
23
23
  - **Core is bundled in.** `Bun.build` bundles the server + bin entrypoints to
24
24
  plain JS with `@runcastle/core` resolved into the output (not `--compile`).
25
- Every real dependency (node-pty, simple-git, hono, drizzle, …) stays external
26
- so it installs normally and keeps its prebuilds — the tarball's dependency tree
27
- carries no `workspace:*`.
25
+ Every real dependency (simple-git, hono, drizzle, …) stays external so it
26
+ installs normally — the tarball's dependency tree carries no `workspace:*`.
28
27
  - **Patched dependencies are bundled in too.** A workspace `patchedDependencies`
29
28
  patch never reaches a user's install, so a patched dep must either be inlined
30
29
  (`BUNDLED_DEPENDENCIES` in `scripts/publish-manifest.ts` — sandcastle, with
31
30
  its own runtime deps folded into the manifest) or be listed as external with a
32
- written reason the patch is unnecessary there (`PATCHED_EXTERNAL_DEPENDENCIES`
33
- — node-pty). The build fails on any patch with neither fate, and checks the
31
+ written reason the patch is unnecessary there (`PATCHED_EXTERNAL_DEPENDENCIES`,
32
+ empty today). The build fails on any patch with neither fate, and checks the
34
33
  emitted bundle for the patch's code so a registry copy cannot slip in
35
34
  (ADR-0011; this is how v1.2.11's burns all died).
36
35
  - **Runtime assets ship as real files.** The drizzle migrations, the hook client
37
- (spawned by `bun`), the PTY sidecar host (spawned by `node`), the skills pack +
38
- burner prompts, and the built SPA are copied beside the bin — they can't live
36
+ (spawned by `bun`), the skills pack + burner prompts, and the built SPA are
37
+ copied beside the bin — they can't live
39
38
  inside a bundle because separate processes read them by path.
40
39
  - **One resolver, both layouts.** `src/launcher/asset-paths.ts` resolves every
41
40
  such asset via an env override that wins-and-fails-loudly, else the workspace