| 1 | ## Summary |
| 2 | |
| 3 | - |
| 4 | |
| 5 | ## Issues |
| 6 | |
| 7 | <!-- |
| 8 | If this resolves a report, put `Fixes #123` on its own line — GitHub only |
| 9 | auto-closes from a bare line, so `- Fixes #123` in a list does nothing and the |
| 10 | report stays open. If it only relates to one, use `Refs #123` instead: the |
| 11 | release workflow then asks that reporter to verify once the fix ships. |
| 12 | --> |
| 13 | |
| 14 | ## Verification |
| 15 | |
| 16 | - |
| 17 | |
| 18 | For a GSAP to WAAPI/CSS migration (or any cross-API replacement), document |
| 19 | the source-to-target contract here: easing syntax, time units, callbacks, |
| 20 | cancellation, reduced-motion behavior, and failure fallback. Verification must |
| 21 | assert that the target API was actually called; a mock that silently skips it |
| 22 | does not count. |
| 23 | |
| 24 | ## Documentation impact |
| 25 | |
| 26 | Documentation-impact: TODO |
| 27 | |
| 28 | For changes to user-visible CLI, Desktop, configuration, provider, permission, |
| 29 | or tool behavior, use one of: |
| 30 | |
| 31 | - `Documentation-impact: updated - <what changed>` and update `docs/*.md`. |
| 32 | - `Documentation-impact: none - <why the embedded documentation remains correct>`. |
| 33 | |
| 34 | ## Cache impact |
| 35 | |
| 36 | Cache-impact: TODO |
| 37 | Cache-guard: TODO |
| 38 | System-prompt-review: N/A |
| 39 | |
| 40 | For cache-sensitive changes, fill these lines before requesting review: |
| 41 | |
| 42 | - `Cache-impact`: `none`, `low`, `medium`, or `high`, plus the reason. |
| 43 | - `Cache-guard`: the focused guard test/command added or run, or why an existing guard covers the change. |
| 44 | - `System-prompt-review`: required reviewer/approval note when provider-visible system prompt, memory prefix, output style, or skill index behavior changes. |
| 45 |