With-Grounding Fixture

This fixture exercises the v8 rule non-empty project[] → grounding required. It also carries keywords so routing-quality checks have realistic activation metadata to inspect, but keywords are not schema-required.

Concept of the skill

What it is: A project-anchored skill declares which projects it belongs to (project[]) and grounds its claims in those projects' truth sources (grounding). Mental model: Project membership implies repo-specific claims, which the schema makes grounding mandatory for. Why it exists: To prove the v8 rule that a non-empty project[] requires a populated grounding block (re-anchored from the retired deployment_target: project rule). What it is NOT: It is not a portable/ambient skill (those carry no project[] and need no grounding), and public: false here marks it as not-for-marketplace, independent of grounding. Adjacent concepts: grounding, project[], drift detection, the public publishability gate. One-line analogy: Grounding is a citation; a project-anchored claim without it is hearsay. Common misconception: That publishability (public) drives the grounding requirement — it does not; project[] presence does.

Coverage