Ramnique Singh 8cf1335577 refactor(x): make capability activation a discriminated union; fence the loadSkill path ... The design rule "app/always capabilities are never model-loadable" was held only by two arrays happening to be separate. Now it is structural: CapabilityDefinition is a union — ModelCapability (requires catalog title/summary and lazy content, cannot carry a fragment) vs EagerCapability (requires promptFragment, never enters the catalog) — and DiskSkill is typed as ModelCapability, making the disk trust boundary a compile-time fact instead of a comment. The kitchen is fenced along with the menu: catalog building and skill-tool attachment go through pure, fenced helpers (buildCatalogFromEntries / toolNamesFromEntries), and the boundary test now feeds a real eager capability through a mixed list and asserts both the catalog hides it and the tool path refuses its tools. Golden snapshots unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-10 08:38:51 +05:30
..
docs	refactor(x): one delivery path for turn events — chat, channels, deltas	2026-07-09 15:47:21 +05:30
scripts	Code mode: make packaged builds work via managed engine provisioning (#625)	2026-06-17 21:53:15 +05:30
src	refactor(x): make capability activation a discriminated union; fence the loadSkill path	2026-07-10 08:38:51 +05:30
.gitignore	bootstrap new electron app	2026-01-16 12:05:33 +05:30
package.json	feat(apps): M3 groundwork — packager, GitHub device-flow auth, registry client	2026-07-06 14:49:52 +05:30
tsconfig.build.json	Refactor builtin file tools beyond workspace scope	2026-05-25 16:21:51 +05:30
tsconfig.json	feat: extract presentation generator into executable code with builtin tool	2026-01-30 13:30:06 +05:30
vitest.config.ts	Refactor builtin file tools beyond workspace scope	2026-05-25 16:21:51 +05:30