wakeflow-target-craftlisted

# Wakeflow Target Craft Load this alongside `wakeflow-target`. `wakeflow-target` governs the immutable dispatch packet, window boundaries, strict `TargetResult` recording, and return transport — the "how do I interact with the state machine". THIS skill governs the "how do I write the code well" so acceptance passes on the first pass instead of looping through rework. ## Core stance The target must leave structured, reproducible REVIEW INPUTS, not a "looks done" claim. Wakeflow can check that required kinds and mappings exist and that exact declared ref/digest tuples are linked; it cannot establish that the referenced contents are true. Every craft practice below exists to give the controller something concrete to inspect and independently rerun before acceptance. Craft prepares an honest review; it does not earn acceptance by itself. **NO IMPLEMENTATION UNTIL EVERY AUTHORED `acceptanceAnchor` HAS A PLANNED RED TEST OR PROBE; NO COMPLETED RESULT UNTIL EVERY ANCHOR MAPS TO EXACT EVIDENCE REFS.** Violating the letter of this rule is violating its spirit. - Read the package's `objective`, `requirementRefs`, complete `boundaries`, `completionExpectations`, `acceptanceAnchors`, and advisory `designIntent` before planning code. - For each anchor, record `id -> test/probe seam -> expected RED -> expected GREEN`. Use the exact confirmed claim; do not widen it. - If an anchor is untestable, conflicts with another authority, or requires missing facts, return `needs-review`