* Allow context roots to be declared in .impeccable/config.json
Monorepo detection previously read workspace roots only from package
managers (package.json workspaces, pnpm-workspace.yaml, lerna.json),
coupling "where design context lives" to the dependency graph. Add a
`contextRoots` glob list to .impeccable/config.json / config.local.json
so non-JS repos -- and design-context boundaries that don't match
packages -- can declare nested PRODUCT.md/DESIGN.md roots directly.
The new source is folded into readWorkspacePatterns(), so detection,
project resolution, and the app picker pick it up unchanged. Negation
and config.local.json extension work for free.
* Define projectRoots composition with package workspaces
Address review feedback on #307:
- Rename the config key contextRoots -> projectRoots: the globs establish
project boundaries and app-picker targets, not just where context files
live.
- Make cross-source precedence explicit: a path matched by any impeccable
pattern, positive or negated, is governed by the impeccable group alone;
package-manager patterns fill in the paths it does not match, and `!`
negations apply only within their own source. readWorkspacePatterns()
becomes readProjectPatternGroups() / readProjectPatterns(), with package
workspaces as one discovery source.
- Drop app-picker candidates that would resolve elsewhere: a package
workspace subsumed by a broader impeccable boundary is no longer listed,
since choosing it would silently resolve to that boundary.
- Add five composition tests and document the key in the config and
context reference pages (path relativity, glob and negation syntax,
shared/local merge, precedence).
CypherPoetandGitHub
a6957e5d4b