Origin: rickardvh/agentic-workspace#1253
The AW seam review found that generated TypeScript package resources can carry the full command package record, including Python runtime binding metadata, even when the generated package declares a Node-only runtime model. A full cross-target resource may be intentional for introspection, but the generator should either expose a target-scoped projection or document/enforce why every generated target ships the full cross-target package record.
Acceptance:
- Decide whether generated target packages should ship a full package record or a target-scoped command package resource.
- If target-scoped, render resource metadata that omits target-irrelevant runtime bindings such as Python runtime binding details from TypeScript-only runtime packages.
- If full cross-target metadata is intentional, document the invariant and add a test proving target runtimes do not treat target-irrelevant bindings as executable fallback behavior.
- Include a fixture/check covering TypeScript or another non-Python target.
This is a generator-side follow-up from the AW #1253 seam review.
Origin: rickardvh/agentic-workspace#1253
The AW seam review found that generated TypeScript package resources can carry the full command package record, including Python runtime binding metadata, even when the generated package declares a Node-only runtime model. A full cross-target resource may be intentional for introspection, but the generator should either expose a target-scoped projection or document/enforce why every generated target ships the full cross-target package record.
Acceptance:
This is a generator-side follow-up from the AW #1253 seam review.