docs: capture tonight's rulings — record-OR-stream (never both), scheduling scope, SYNC provenance, playout declined

- Modes: creator ruling 2026-09-01 — the VOD is the copy; dual encode degrades both
  outputs on mediocre hardware ('we're not them'). ai.md 'cheap on NVENC' claim
  retired; TASK 18 three-modes -> two; pills-become-radios noted as PENDING code.
- Design Principle gains 'we're not them' (hardware realism) as its fifth bullet.
- TASK 34 scope: countdown+notify live scheduling is the whole story — 'going live is
  our schedule'. Scheduled playout discussed & DECLINED; premiere/upload + playout +
  simultaneous-record-stream added to the closed out-of-product table.
- TASK 22: SYNC slider provenance restored — creator-requested (OBS delay-filter fix,
  native). Placement question stays open; capability does not.
- MyMistakes: the provenance rule (a fact without its who/why becomes a future argument).
Docs only — zero code in this commit, per creator instruction.

MyMistakes.md

@@ -146,3 +146,15 @@ Bonus: the "failing" test encoded the MAP's contract (`loopbackGain = GameAudioV
 code had drifted to unity on a disproven premise (loopback capture does NOT follow endpoint
 volume — creator's 20%-volume/pegged-meter observation killed it). The test was right all
 along — failing tests may be the last honest witnesses; interrogate, don't pardon.
+
+## Feature provenance: record WHO asked and WHY, in the task entry itself
+
+(2026-08-31/09-01, the SYNC slider scare) TASK 22's lip-sync slider surfaced on the preview rail and
+the creator's reaction was "totally don't remember ordering that" — because the queue entry recorded
+WHAT shipped (a slider, 0-500ms, a converter class) but not WHO asked (the creator, explicitly, for
+OBS's delay-filter fix built natively). Eight days later his own request read like AI drift and nearly
+got deleted. Rule: the moment a creator-driven feature is queued or shipped, its entry carries a
+one-line provenance — *who asked, what triggered it* ("creator: OBS delay-filter lip-sync fix, native").
+Features without attribution become roadmap orphans that get punted, removed, or re-litigated. Same
+disease as an unexplained "known failure" label — a fact recorded without its reason is a future
+argument.