Seamless Porting

Essential: treat Seamless pipeline work as a staged, non-linear progression. Seamless wrapping syntax is deceptively small: a minor syntactic change can have large semantic and operational effects. Agents mispredict Seamless behavior when they change wrapping, wiring, capability activation, execution placement, and optimization at the same time.

The purpose of this skill is attention routing. Consider exactly one active concern at a time, but do not treat the active concern as a physical edit boundary. Seamless changes often touch several surfaces at once: step code, wrapper syntax, wiring, data movement, cache policy, backend configuration, and granularity. The active concern governs why the edit is being made, what evidence is relevant, and which exit check must pass.

Operating Model

Stages have a normal order, but the active concern is chosen by user intent, failure evidence, failed prerequisites, or the earliest unfinished concern.

Before nontrivial edits, state or infer:

• Active concern:
• Why this concern:
• Touched surfaces:
• Exit check:

Concern selection priority: