docs: describe agentseam as the layer for every coding agent

[jothimani-rajendran]

What

The family map in docs/ecosystem.md called agentseam "the primitives layer under chock". agentseam is a general layer for building any plugin or agent primitive for any coding agent; chock is one thing built on it, not the frame. The agentseam row now reads, in the wording every sibling repository's family table uses:

The primitives layer for every coding agent: one handler API over their hooks, instruction files, plugin packaging and config, with a capability matrix that carries its provenance. chock is one thing built on it

The row's previous tail ("chock's plugin packaging consumes it at build time") is folded into "chock is one thing built on it" so the wording stays identical across repositories. One line changes; nothing else in the page or the README is touched, and no count is typed.

Definition of done

Documentation only: no policy, artifact, manifest or check changes, so the chock commands and the acceptance suite are not affected.

• pytest -q tests/test_repo_standards.py green (1 passed; the page stays within the line budget)
• chock check → n/a, no artifacts changed
• chock check --only matrix → n/a, no behaviour changed
• chock sync --repo . --check → n/a
• chock check --only verify → n/a
• Registry rescanned → n/a
• pytest acceptance/ → n/a, packaging unchanged
• Existing artifacts migrated → n/a
• Touched manifests → none
• ruff check . / ruff format --check . → no Python changed

Claims

• No surface is described as enforcing more than it installs. The row describes agentseam's scope, not any enforcement level, and states no count.

🤖 Generated with Claude Code

---

Generated by Claude Code