[Brian Krabach (bkrabach)]

User-directed scope

The user explicitly waived the outstanding 10 IC-10 profiling cases and 2 IC-09 connected-document overlay cases after receiving context about these optional integrations, and requested repository notes to prevent repeated source requests/readiness blockers.

Changes

• Record the dated, exact-scope waiver and future reactivation rule in docs/validation/integration-coverage.md; replace obsolete unconditional source/qualification instructions.
• Add a concise pointer in AGENTS.md and a profiling-specific note in docs/DEPLOYMENT.md.
• Update only the two descriptive prerequisite strings in scripts/integration-coverage.json.

Waived for readiness is NOT passed or execution-qualified. Tests, frozen baseline evidence, selectors, path rules, lane modes, workflows and branch protections remain unchanged. Other checks, voice/physical acceptance, DTU approvals and performance measurement are not waived. Future explicit adoption/change needs a scoped acceptance decision plus canonical clean source and exact revision; missing inputs or a generic audit alone do not reopen this obligation.

Verification

• git diff --check passed.
• Standard-library JSON/AST check confirms exactly 2 connected-document and 10 profiling cases; all manifest data except the two descriptive strings is unchanged; waiver links resolve.
• Independent read-only four-file review: CLEAR, exact hashes matched by parent.
• No app imports, optional integration executions, installations, environments or live effects. This documentation change is not fresh runtime qualification.

Integration

Docs/metadata-only change on 0ae9528. Existing Release owner retains integration/publication authority; no separate app release requested.

[Brian Krabach (bkrabach)]

Independent review CLEAR at afa5c11. I read the original saved user decision and the immediately preceding explanation: the scope is the ten optional profiling cases and two connected-document overlay cases, not other integration, runtime, voice, physical-device or performance checks.

All four changed files were reviewed. The documentation preserves earlier evidence, calls these cases waived for readiness and execution-unqualified (never PASS), requires a deliberate scoped decision for future reactivation, and preserves strict checks if a lane is deliberately run. Independent parsed-manifest comparison confirms only /lanes/connected-documents/prerequisite and /lanes/profiling/prerequisite strings changed; selectors, modes, path rules and every other manifest field are identical. No workflow, assertion, branch protection, runtime, version or asset change.

All current selected checks are terminal:10SUCCESS/1manual default-installedSKIP. Synthetic123dc0fce9f33bb3f0c8d7edeae8cde03b260867/tree7a909b944c293341c8e5077bcf36ea2b6fc423a7 exactly matches the reviewed head on main0ae952. Accepting this repository-guidance integration under standing Unified authority. No new app publication; staged0.72.5 bytes remain immutable. This docs result is not adoption or executed optional-integration qualification.