Feature request: .commandcode/rules/ always-on project rules (like grok)

Problem

Command Code loads AGENTS.md memory files, but nested/directory rules are loaded only on demand (when a file under that directory is referenced). There is no always-on project-rules mechanism equivalent to grok rules loading (AGENTS.md / CLAUDE.md / .grok/rules/*.md from repo root down, every session).

This means conventions that must apply globally to every session (orchestration roles, code-style rules) cannot live in a directory the agent is not currently touching — they silently do not load.

Proposed feature

1. Support a .commandcode/rules/ directory that loads every *.md file inside it on every session (like grok .grok/rules/), in addition to AGENTS.md.
2. Load these rules always, not on-demand — project conventions, not directory-scoped context.
3. Scope by directory tree like grok: deeper directories take precedence on conflicts (nearest wins).
4. Keep AGENTS.md behavior unchanged; .commandcode/rules/ is additive.

Why it matters

Right now the only way to make a nested rules file always-on is to manually @path-import it from the root AGENTS.md. A dedicated always-on rules directory makes the intent explicit and keeps multi-file conventions organized without editing the root file.

Example

repo/
  AGENTS.md
  .commandcode/rules/
    orchestrator.md   # always loaded
    code-style.md     # always loaded

Alternatives considered

• Using @path imports from the root AGENTS.md (works, but requires hand-editing the root file and does not scale).
• Nested AGENTS.md files (load only on-demand, not always).

Start by tracing the existing AGENTS.md loading behavior and how nested rules are currently loaded on demand. Use the proposed .commandcode/rules/ layout and nearest-directory precedence as acceptance criteria; done means every matching Markdown rule loads each session while AGENTS.md behavior remains unchanged.