ADR-0011: Version baseline and execution gates

Date: 2026-10-11. Status: accepted for implementation; database compatibility requires live verification.

Use installed SDK 10.0.401 with roll-forward disabled, EF Core 10.0.12 and Neo4j.Driver 6.3.0. Packages restore successfully together for net10.0. Central versions and generated dependency locks make builds reproducible. Verify provider-facing signatures against EF tag v10.0.12 (commit 001bfac21c1910cdf1110ca256c9ea0a06f374ca).

The user's mission extends beyond the kickoff-only prompt embedded in START_HERE. Execute the full backlog in dependency order, preserving live evidence gates. No tooling project may become a prerequisite of the core provider. Optional tooling is later work, not silently deleted scope.

Specialist tasks use disjoint file ownership in the shared workspace; the root agent integrates and runs combined checks. The initial verified provider checkpoint was published as ff283a3 to the configured private repository to execute the required hosted CI gate.

Only disposable loopback Neo4j is used for integration. Credentials are ephemeral and ignored. Schema changes belong to explicit fixture setup or later reviewed schema operations; runtime querying must never perform implicit DDL.

Revisit pins only with matching source review and full relevant regression tests. SDK and NuGet sandbox access requirements are environment limitations, not provider limitations.

Hosted runner resource policy

The first Linux CI run passed restore/build/unit/policy checks but refused fixture startup: 6.79 GiB was available, below the local shared-machine startup requirement of 7 GiB. The local reserve protects a second developer agent; the fresh GitHub-hosted VM has no such shared workload.

CI therefore explicitly opts into a dedicated hosted policy, guarded by GITHUB_ACTIONS=true and RUNNER_ENVIRONMENT=github-hosted. It retains a 2 GiB reserve, 0.5 GiB headroom and 1.5 GiB fixture budget. Local and self-hosted execution retain the 5 GiB reserve. Ownership, one-container checks, resource inspection and bounded container limits remain active. This is a preflight policy, not continuous memory enforcement. See the version/capability matrix and execution evidence (maintainer-local record) for tested profiles and CI outcomes.