consumer-fixture

Cross-skill handoff validation is performed by running a test fixture that checks consumer prose for required field-name tokens. This fixture omits the token to trigger and verify failure paths in automated test suites.

A consumer fixture is a controlled test artifact, not a functional skill, used to exercise cross-skill validation logic. It verifies that consumer skills properly declare required field-name tokens when referencing partner schemas.

You test missing-field-name errors in CI pipelines by integrating this fixture into your automated test suites. It triggers the failure path to confirm your detection logic properly flags omitted field-name tokens during consumer skill integration.

No external runtime dependencies are required to run cross-skill handoff validation fixtures. They operate using only local repository fixtures to validate that consumer prose includes the declared field-name token.

Yes, you can use this fixture to verify safety checks for partner schemas. It serves as a controlled input for test suites to ensure proper error reporting when consumer-facing prose fails to declare required tokens.

Cross-skill handoff validation fails because the consumer-facing prose must explicitly declare required field-name tokens from partner schemas. This fixture deliberately omits the token to trigger and test that specific failure path.