Curate and split the default smoke aggregate

[chubes4]

Problem

The default npm run check aggregate currently launches 344 commands: 332 discovered files, three declared chains, and nine serial integrations. TypeScript tests run as separate tsx --no-cache processes, heavyweight Playground/browser coverage shares the default lane, and seven files are explicitly excluded as failing and unmaintained; pending triage. A single late failure forces the entire 10-12 minute aggregate to restart and obscures ownership.

Desired outcome

Create a fast deterministic default contract lane and explicit owned integration lanes. Audit every acknowledged stale exclusion and overlapping outcome test, then delete obsolete coverage, consolidate duplication, or assign expensive environment coverage to its authoritative workflow. Keep release-level exhaustive coverage without making every focused PR replay one monolithic process farm.

Acceptance criteria

• Every current stale exclusion is classified as delete, repair/promote, or environment-owned with evidence.
• Default checks exclude heavyweight environment integrations through named owned lanes, not vague skip reasons.
• Duplicate outcome coverage is consolidated without reducing user-facing behavioral protection.
• Serial and chain-owned lists contain only tests that require ordering or isolation.
• Before/after command count and wall-clock evidence is recorded.
• Focused, default, and release/owned gates all pass.

AI assistance

GPT-5.6 Sol via OpenCode identified the aggregate topology and stale exclusions, and drafted this curation tracker under Chris Huber's direction.