Clarify DMC routing and remove snapshot inventory from AGENTS.md

[chubes4]

Problem

The DMC AGENTS.md section mixes authoritative workspace policy with exhaustive command lists, optional file-I/O ceremony, duplicated WordPress source warnings, and a separate Workspace Inventory snapshot. The inventory says live state should be queried, then embeds counts/state that become stale and consume context on every task.

The boundary with Homeboy is also unclear: both sections appear to own worktrees, evidence, GitHub, and lifecycle operations.

Desired contract

• State that DMC owns authoritative repository, primary-checkout, worktree, and GitHub workspace state.
• State that Homeboy consumes managed worktrees for agent execution, gates, promotion, evidence, and publication.
• Provide bounded default routing for workspace inspection, worktree creation/finalization, primary refresh, and GitHub state.
• Keep primary read-only and freshness safety contracts.
• Keep native local file I/O guidance without advertising exhaustive DMC file verbs.
• Identify the generated path as the controller workspace root.
• Remove the generated Workspace Inventory section and direct agents to live workspace list|show|hygiene commands.
• Avoid repeating the full WordPress source-path policy owned by wp-coding-agents.

Acceptance criteria

• DMC contributes one concise headed section with explicit ownership/routing/discovery.
• workspace-inventory is no longer registered or rendered.
• No repository/worktree counts are injected into AGENTS.md.
• DMC has a unique deterministic priority between Data Machine and Homeboy.
• Existing policy filters and primary safety behavior remain supported.
• Tests prove the concise contract and absence of inventory registration.

AI assistance

• Tool: OpenCode
• Model: OpenAI GPT-5.6 Sol
• Used for: Audited the live generated AGENTS.md, traced DMC inventory and command rendering, and drafted this issue with Chris.