test: static template assertions for delete-then-append + revert autoplan E2E shape

5 new static tests in test/gen-skill-docs.test.ts (4 plan-review SKILL.md
files + 1 source resolver) verify the new prompt language is present and
the old contradictory bullets are absent. Synthetic regression check
confirmed all 5 fail when the prompt fix is reverted.

The autoplan E2E (skill-e2e-autoplan-auto-mode.test.ts) reverts to its
original AUQ-blocked-gate-surface shape. The mid-file regression scenario
the plan briefly proposed isn't reachable in the current PTY harness because
--disallowedTools AskUserQuestion makes autoplan bail at the Phase 1
premise gate before any review-write code path runs. Static prompt-text
verification covers the load-bearing change.

test/skill-e2e-autoplan-auto-mode.test.ts

@@ -18,6 +18,16 @@
  * Filename keeps `auto-mode` for branch-history continuity. Auto-mode (the
  * AUTO_DECIDE preamble path when QUESTION_TUNING=true) is a related but
  * distinct silencing mechanism; both share the same fix surface.
+ *
+ * Note on report-at-bottom contract: the GSTACK REVIEW REPORT delete-then-
+ * append flow lives in `scripts/resolvers/review.ts` and is exercised when
+ * reviews actually run. The PTY harness can't drive autoplan through its
+ * review phases without auto-progression of AUQs (see runPlanSkillCounting),
+ * and `--disallowedTools AskUserQuestion` makes autoplan bail at the
+ * premise gate via the plan-file fallback before any review runs. The
+ * report-at-bottom prompt change is verified statically in
+ * `test/gen-skill-docs.test.ts` instead — that's the load-bearing
+ * verification for the contradictory-prompt fix.
  */
 
 import { describe, test, expect } from 'bun:test';