gsap_tween_tail counts GSAP's force3D and autoRound flags as properties

该警告来自 packages/cli/src/utils/gsapTweenTails.ts：NOT_PROPERTIES 列表（约第 77-113 行）缺少 force3D 和 autoRound，而 plainProperties（约第 133 行）仍保留了它们。将这两个键添加到列表中，然后检查 issue 中的复现不再输出 gsap_tween_tail，而真实的共享属性（例如两个 opacity 补间）仍会输出该警告。复现结果干净且现有的补间尾部测试仍然通过时，即为完成。

Describe the bug

check's runtime warning gsap_tween_tail treats GSAP's force3D and autoRound flags as tweened properties.

collectTweenRecords leaves out GSAP's special keys (NOT_PROPERTIES: duration, ease, overwrite, immediateRender, ...) but not force3D or autoRound. So tailBetween finds a shared "property" in any two overlapping tweens of one element that both pass them, whatever they animate, whenever the earlier one ends up to 0.25 s after the later one.

A composition that passes force3D: false, autoRound: false on every tween (ours does, for crisp scaled text) gets a warning for every such pair: about 60 on a 65 s composition, every one naming only force3D, autoRound, none a real property.

That hides the case the warning is for. We had two genuine pairs (two tweens of opacity on one element at once), found by their frames once 0.8.158's seek drew them in another order, and they were lost among the flag-only warnings.

Measured on 0.8.158 (0.8.152 has the same list). The code is unchanged in v0.8.162: NOT_PROPERTIES has neither key (packages/cli/src/utils/gsapTweenTails.ts, lines 77-113), and plainProperties keeps every other key of vars (line 133).

Minimal reproduction

npx hyperframes init repro --non-interactive --example blank

Then replace repro/index.html with the file below. Only the <script> differs from the blank template: one element, two overlapping tweens of different properties (x, then opacity), both with force3D: false, autoRound: false. The earlier tween ends 0.1 s after the later one.

<!doctype html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=1920, height=1080" />
    <script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/gsap.min.js"></script>
    <style>
      * {
        margin: 0;
        padding: 0;
        box-sizing: border-box;
      }
      html,
      body {
        margin: 0;
        width: 1920px;
        height: 1080px;
        overflow: hidden;
        background: #0a0a0a;
      }
      #root {
        width: 100%;
        height: 100%;
        display: flex;
        align-items: center;
        justify-content: center;
        font-family: Inter, ui-sans-serif, system-ui, sans-serif;
      }
      #title {
        color: #f4f4f5;
        font-size: 72px;
        font-weight: 600;
        letter-spacing: -0.03em;
      }
    </style>
  </head>
  <body>
    <div
      id="root"
      data-composition-id="main"
      data-start="0"
      data-duration="10"
      data-width="1920"
      data-height="1080"
    >
      <h1 id="title" class="clip" data-start="0" data-duration="10" data-track-index="0">Title</h1>
    </div>
    <script>
      const tl = gsap.timeline({ paused: true });
      // One element, two overlapping tweens of different properties (x, then opacity).
      // The earlier tween ends 0.1 s after the later one. Both pass force3D and autoRound.
      tl.to("#title", { x: 200, duration: 1, force3D: false, autoRound: false }, 0);
      tl.to("#title", { opacity: 0.5, duration: 0.4, force3D: false, autoRound: false }, 0.5);
      window.__timelines["main"] = tl;
      tl.seek(0);
    </script>
  </body>
</html>

Steps to reproduce

1. Set up the reproduction above.
2. In repro, run npx [email protected] check --json.
3. Look at runtime.findings: one gsap_tween_tail warning naming force3D, autoRound.
4. For comparison, remove , force3D: false, autoRound: false from both tweens and run the check again: runtime.findings is empty.

Expected behavior

No gsap_tween_tail warning. The two tweens share no tweened property (x and opacity). force3D and autoRound are GSAP flags, not properties a tween animates, so they should be left out as ease and overwrite are, and the warning should name only properties two tweens really share.

Actual behavior

check --json exits 0 with this runtime finding (other fields trimmed):

{
  "code": "gsap_tween_tail",
  "severity": "warning",
  "message": "In timeline \"main\", a tween on force3D, autoRound of #title ends at 1.000 s, 0.100 s after a later tween on force3D, autoRound ends at 0.900 s. For that tail the earlier tween takes force3D, autoRound back and leaves its own end value on screen, so the later tween's end never shows. End the earlier tween by 0.500 s, or add overwrite: \"auto\" to the later tween.",
  "sourceFile": "index.html",
  "time": 0.9
}

The same composition without the two flags has no runtime findings.

Environment

OS:          Windows 11 (build 26200)
Node.js:     v24.14.0
HyperFrames: 0.8.158 (0.8.152 has the same NOT_PROPERTIES; code unchanged at v0.8.162)
Chrome:      Chrome Headless Shell 152.0.7977.30

Additional context

Request: add force3D and autoRound to NOT_PROPERTIES (or leave out every GSAP flag that is not a tweened property), so the warning names only properties two tweens really share.