v0.1.35

Workspace-scoped control root

When no WTC_CONFIG_ROOT is set and a collection has no generated root, the CLI now uses <workspace-root>/.config. Separate workspaces therefore have separate default locations for secrets and tool configuration. An explicit WTC_CONFIG_ROOT still takes precedence, followed by the value already recorded in .env.collection.

Existing collections keep their recorded root. This release does not move or copy credentials. To migrate a collection, set WTC_CONFIG_ROOT to the intended workspace .config directory and run wtc env setup; reload any already-open panes afterward.

wtc secrets list and wtc env list describe control-root files and wtc.env as shared by collections using that root, without displaying values.

Catch-up secrets hook

wtc catch-up now skips secrets linking for selected external siblings that are not registered repositories. Registered repositories and the harness still run the hook. The decision uses the target's current registry after a harness update, and the report records a skipped hook for unmanaged siblings.

Verification

The CLI test suite, vet, PR checks, and exact main builds passed for both changes. Regression tests cover default and explicit control-root precedence, inventory scope labels, and mixed registered/unmanaged catch-up targets.