Skip to content

[Docs]: Bind core/Lab isolation and synchronous activation in the invariant index #5121

Closed

Description

@lidge-jun

Documentation problem type

Incorrect documentation

Documentation location

structure/overview.md:90, structure/adapters/compatibility-lab.md, tests/lab/core-lab-boundary.test.ts

What is wrong or missing?

The root agent guidance declares core/Lab import isolation and synchronous activation non-negotiable, and a transitive mutation-tested guard exists, but the overview invariant index has no corresponding stable binding. tests/lab/core-lab-boundary.test.ts:20 and tests/lab/core-lab-boundary.test.ts:991 already own enforcement.

What should the documentation explain instead?

Add a stable invariant ID tying both guarantees to the existing guard, with a backlink in the test and a link from the Lab contract document. Preserve the guard and its current negative coverage.

Suggested wording or example

“INV-LAB-01: the protected core entrypoints cannot reach optional Lab runtime imports; gated Lab activation remains synchronous before startServer returns.” Check that this ID is unused before implementation.

Additional context or attachments

Pinned source: 7864869c31c41cca9830d93540238f17df8faafb. Static documentation/source comparison only; no runtime test result is claimed.

Update structure/overview.md, structure/adapters/compatibility-lab.md and an existing test comment/describe label. Use the existing invariant binding checker and focused guard in implementation; no new runtime mechanism is needed. Closed #4704 hardened the guard, not this documentation binding.

Checks

  • I searched existing documentation issues.
  • No secrets or personal information are included.

Activity

  1. added a commit that references this issue on Sep 19, 2026
    5ce51cb
  2. lidge-jun commented on Sep 19, 2026

    @lidge-jun
    OwnerAuthor

    Resolved by #5138, merged into dev as 5ce51cb554b333c9b369baf1b15b5d04047c85b4.

    INV-LAB-01 now binds core/Lab isolation and synchronous activation to the existing guard, with test and contract backlinks. Wording accurately distinguishes transitive load-time edges, direct dynamic imports and sanctioned deferred activation. The manifest and generated index include the composition-root ownership. Existing guard assertions and negative coverage were preserved.

    Reviewed head 6986fc6b2391f9b07dc6587e094aea95377c6ca8 passed hosted run35434996760, including structure binding, applicable Linux/macOS jobs and aggregate CI. Review findings were resolved. The actual merge and ancestry in dev were verified. Local suites/tests/typecheck/build were NOT RUN; cumulative dev checks remain monitored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions