[r4ravi2008]

Summary

Rule bootstrap scripts used to run inside the directory walk. A non-zero exit aborted filepath.Walk, so later rule files in that directory were never discovered. On a lenient search path this became a single "skipping directory" warning and the remaining rules were dropped with no per-file signal.

This change discovers and expands one rule directory first, then runs that directory's bootstrap scripts. Bootstrap for a directory finishes before the next directory is discovered, so search-path order is unchanged.

Changes

• pkg/codingcontext/context.go: split discovery (discoverPendingRule) from bootstrap/publication (bootstrapAndPublishRules).
• Lenient paths: a bootstrap failure logs a warning, excludes only that rule, and continues with later rules in the same directory.
• Strict paths: a bootstrap failure is still fatal. Rules after the failing bootstrap are not published.
• Parse or expansion errors still stop discovery of the rest of that directory. On a lenient path, rules already discovered remain eligible for bootstrap, and processing continues with the next directory.
• docs/reference/search-paths.md: document the new failure handling.

Testing

• go test -race -count=1 ./pkg/codingcontext/
• New coverage in context_bootstrap_isolation_test.go:
  • lenient bootstrap failure skips only the failing rule
  • strict bootstrap failure is fatal
  • directory discovery completes before that directory's bootstraps
  • bootstrap of directory N completes before discovery of directory N+1
  • lenient parse failure keeps earlier rules and does not block a later search path

Line Changes

Category	+ Added	- Deleted
Tests	312	0
Docs	18	0
Main code (pkg/codingcontext)	92	33

Definition of Done

• Lenient bootstrap failure excludes only the failing rule
• Later sibling rules in the same directory are still discovered and published
• Strict bootstrap failure remains fatal
• Search-path order is preserved across directories
• Reviewer approval