Namespacing: qualified names for component libraries

[FBumann]

The single most concrete missing primitive for component libraries (see the composition model in ARCHITECTURE.md): merging storage.yaml and chp.yaml today collides on names like eta/flow — extend() merges by name with override semantics.

Needed: qualified names (storage.soc, chp.flow_out) or prefix-on-import, applied at schema-merge time so templates stay authored in their own local vocabulary. Interacts with expressions/macros (references inside a template must resolve within its namespace) and with the port/flow convention (the shared flow variable and connectivity dims are deliberately not namespaced — they are the coupling surface).

🤖 Generated with Claude Code

[FBumann]

Scheduling note — breaking-surface cluster. This sits with #29 (namespacing), #50 (shape-operator renames) and #67 (version policy). All are cheap now and expensive after the first real user, so they are time-boxed by adoption, not by effort.

They should resolve before the package is promoted anywhere. Worth treating as one scheduling decision rather than three independent ones.