wakeflow-test

Wakeflow Test

Load this Skill alongside wakeflow-target. The target Skill owns receipt, identity, exact Test-step mapping, result recording, and return transport. This Skill owns only the Test method inside the frozen card/package boundary.

Iron Laws

TEST EXECUTES ONLY A CONTROLLER-FROZEN QUESTION, ENVIRONMENT, PLAN, AND METHOD. Violating the letter of this rule is violating its spirit.

PRODUCT SOURCE IS READ-ONLY, ALWAYS. A Test card cannot authorize product implementation or repair. Test may inspect product code and diffs, but must not edit, format, generate, vendor, commit, or otherwise mutate product source, tests, configuration, or documentation. Read-only inspection may explain a mapped Test observation; product-diff and target-result review remain controller work.

TEST EVIDENCE IS REVIEW INPUT, NEVER CONTROLLER ACCEPTANCE. A self-review, passing run, or strict TargetResult cannot accept implementation or complete a demand.

Wakeflow Role And Entry Gates

Proceed only through one of these controller-owned routes:

1. Controller-accepted implementation validation: every active required non-Test target for the scope is already accepted, valid superseded history is excluded, and controllerSelfChecks explains what was independently verified and which real-environment risk remains.
2. Controller-scoped Test-only diagnostic: the controller explicitly bounded a reproduction or environment diagnostic that does not depend on unfinished implementation acceptance.

If neither route is explicit, return blocked or needs-review. Do not infer that a smoke-test request, accessible environment, or available time opens a Test scope.

Required Inputs

Read the immutable dispatch packet plus its exact TaskPackage and TestCard references, then verify:

• testContract.executionContract.requirementGoal and the exact controller question in the TestCard boundaryGate;
• testContract.executionContract.approvedPlan and zero-based step mapping;
• confirmed Test Environment Spec and allowed operations;
• controllerSelfChecks or the explicit Test-only diagnostic boundary;
• exact executionContract.allowedSkills, setup policy, attempt bound, restart rule, change control, success, failure, invalid conclusions, and stop conditions;
• TestCard evidenceRequired, packet reviewInputContract, and strict resultContract.