issue-tracking: status/incoming - Stubs werden ausgearbeitet, nie so umgesetzt (4.7.5-beta.1, #62)

Files changed:
- CHANGES.md
- VERSION
- instructions/dev/issue-tracking.md
- instructions/dev/stack-dev/SKILL.md

instructions/dev/stack-dev/SKILL.md

@@ -48,8 +48,10 @@ stack development happens in the origin repo instead (see AGENTS.md's routing li
    moves, so an interrupted session leaves a body the next one can resume from, *and* rewrite it
    to its final state before closing. Both halves bind; the second is what
    [`stack-close`](../stack-close/SKILL.md) carries out once this skill's own work is published -
-   see step 5 below. Read it before filing something for later, before editing or closing an
-   issue, or before deciding what to pick up next.
+   see step 5 below. An issue labelled `status/incoming` is the exception to all of that: it is a
+   human's stub, not a spec, and it is **never implemented as it stands** - it gets worked out and
+   triaged first. Read this file before filing something for later, before editing or closing an
+   issue, before picking up an incoming stub, or before deciding what to pick up next.
    [testing-conventions.md](../testing-conventions.md) - the suite runs against a deliberately
    empty machine; what the autouse fixture already neutralizes, and what a test still has to
    establish itself. Read it before adding or changing a test.