Complete Studio–Codex bidirectional linkage

[henyjone]

What changed

• adds editable Studio properties with localized values, inline validation, a field-level diff, and an explicit “发送给 Codex” action
• records preview origin, summary, changed fields, and revision while preserving the single .apsal project kernel
• adds apsal_frontend_get_updates plus automatic compact Studio-update reminders in linked plugin calls
• distinguishes Studio-origin and Codex-origin proposal cards and prevents Studio from silently applying its own outbound proposal
• updates the creator skill, version map, upgrade guide, and usage guide

Why

Studio previously projected and confirmed Codex changes, but its properties were effectively read-only and the plugin had no durable inbox for Studio-origin edits. That made the link one-way in normal use.

Impact

Creators can now edit an eligible workflow card in Studio, send the exact semantic diff to Codex, and see Codex apply or reject it against the same revision. Headless Codex workflows remain unchanged.

Validation

• python3 -m pytest -q — 78 passed
• npm test -- --run — 5 passed
• npm run build — passed
• npm run test:electron — 3 passed
• installed APSAL Studio 0.2.0 and completed a live Studio r1 → proposal r2 → Codex apply r3 round trip