feat(compiler): [#221] понижать статические NanoProps/NanoOptions, не только opacity

[lemone112]

Что

Закрывает #221 (эпик #220): build-time lowering статических вызовов nano расширен с opacity на любые статические NanoProps/NanoOptions.

• Канон кривых V1 + общий nano-артефакт через V1-парсер.
• Один общий исполнитель: прежний opacity-путь стал адаптером над ним; vite-адаптер на общем планировщике.
• Metafile-proof: conversion math не попадает в браузерный граф.
• Гольф исполнителя: все size-гейты в порогах без подъёма (nano 1011/1024, mixed 17464/17500).

Доказательства (локально)

Тесты 4007 passed (включая новый corpus compiler-nano-multi-lowering); size PASS все гейты; typecheck PASS; audit clean.

История

Пересборка июльской wip-серии (10 коммитов) на актуальный main: rebase без конфликтов, серия сквошнута в атомарный срез.

Контекст плана

Узел NANO-01 трека lab-motion-production. Разблокирует KEYF-02 (#222) вместе с KEYF-01.

Rollback

Revert-PR squash-коммита; публичная поверхность не менялась (compiler-only).

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 17 minutes

Limit details: You’ve used the included review currently available. Your 105 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: f9c1559c-2b1b-4ca7-b99b-c4dee03f475c

📥 Commits

Reviewing files that changed from the base of the PR and between e08c4cb and 0161fba.

📒 Files selected for processing (5)

• src/compiler/core.ts
• src/compiler/runtime/index.ts
• src/compiler/vite/index.ts
• test/compiler-nano-lowering.test.ts
• test/compiler-nano-multi-lowering.test.ts

---

_{Comment @coderabbitai help to get the list of available commands.}

[lemone112]

CI красный честно: ветка раздувает shipped-субпуть compiler/vite 8.95→9.78 KB gz (порог 8.9K, WARN=FAIL) и compiler/runtime 0.33→0.35 KB. Моя локальная проверка перед push была дефектной (считала только строки РЕГРЕССИЯ, не WARN [OPEN ITEM]). Перевожу в draft; следующий шаг — гольф compiler-графа (V1-парсер/канон кривых — главные подозреваемые по metafile) до порогов, без их подъёма.