kelly-app-skill-creator-testslisted

# Kelly App Skill Creator Tests Verify generated Kelly app skills without taking ownership of their product or runtime design. Treat the app source and creator contracts as inputs; never weaken either contract merely to make a test pass. ## Ownership Boundary - `$kelly-app-skill-creator` owns product design and creates the canonical `<skill-root>/app/` project. - `$busabase-app-creator` owns AirApp runtime, SDK, security, sync, and deployment constraints. - This skill owns shared test infrastructure, per-skill fixtures and assertions, OSS/Cloud execution gates, failure artifacts, CI wiring, and test reporting. - Keep pure domain and module tests in `<skill-root>/app/test/`. Keep cross-skill contract, process, browser, Busabase, OAuth, and AirApp tests under the repository-level `tests/app-skills/` tree. ## Required Reading Before changing tests: 1. Read the target skill's `SKILL.md`, canonical `app/`, resource map, checks, and existing tests. 2. Read `$kelly-app-skill-creator` and the runtime rules it delegates to `$busabase-app-creator`. 3. Read `references/test-matrix.md` completely for suite boundaries, environment variables, and required assertions. If a dependency skill is unavailable, inspect its checked-in source when present. Do not invent a weaker replacement contract. ## Workflow 1. Discover canonical apps through `skills/*/app/package.json`. Do not fail legacy `app/` directories that have not yet adopted the canonical contract. 2. Reu