Repository navigation
Project selected provider inputs read-only for agent kits #600
Description
Goal
Discover validated provider inputs from selected pinned kits and project them read-only into sandboxes so agent kits can consume providers without provider-name switches in acq.
Scope
- Consume the generic provider-input contract defined in the Patterns repository.
- Fix caller-visible provider-facts propagation before relying on loaded facts.
- Discover selected provider bundles without a provider allowlist.
- Validate provider facts and model catalogs on the host.
- Project provider-ID-keyed artifacts read-only on SBX and MSB.
- Keep
acqunaware of OpenCode configuration shape. - Implement the provider-input slice of acq: host-authoritative sandbox config — migrate guest-writable state off /var/lib/acq (ADR-0030) #503; broader marker migration remains separate.
Acceptance criteria
- Two fictitious providers are discovered and projected without generic dispatch changes.
- Loaded facts remain visible to callers.
- Provider IDs are unique, safe path components, and agree with their projected directories.
- Malformed facts, malformed catalogs, duplicate provider IDs, undeclared credential variables, and host/URL mismatches fail closed.
- Inputs are read-only in the guest on both supported backends.
- Missing optional providers do not silently become USAi.
- Offline tests cover both backends and multiple providers.
Relationships
Cross-repository milestone parent: GSA-TTS/agentic-coding-patterns#357.
Implements a bounded slice of #503 and includes the prerequisite defect #551.
AI-assisted issue drafting (OpenCode). Human review required.
Activity
mogul commentedon Oct 21, 2026
🤖 First Mate dependency update: implementation is paused without local changes until GSA-TTS/agentic-coding-patterns#518 merges and an immutable Patterns release SHA contains the finalized provider-input validator, schemas, provider-role bundle metadata, and required
apiProtocolfield. The currently pinned Patterns release does not contain those artifacts. Copying the contract into Quickstart or pinning a changing PR SHA would create a competing contract, so this issue remains blocked by the structured cross-repository dependency. Its branch remains stacked above #603 and will resume after the fixed release is available.fix(provider-facts): preserve caller-visible assignments through wrap…
feat(isolation): define provider-neutral input contract (#518)
mogul commentedon Oct 21, 2026
🤖 Dependency unblocked: Patterns
v1.15.0is published at immutable commitf3c6acb4d34a89b3b6539c44d47f56bacaeb94d7and contains the finalized provider-input contract from GSA-TTS/agentic-coding-patterns#518. Implementation has resumed on the linkedfeat/600-provider-input-projectionbranch. The branch will update the singlePATTERNS_KIT_REFto this SHA, validate released bundles host-side, and define the authoritative read-only projection consumed by GSA-TTS/agentic-coding-patterns#516.mogul commentedon Oct 21, 2026
🤖 Implementation blocker confirmed and tracked as #606. The released contract requires
/var/lib/acq/host/models/providers/<providerId>, but current SBX only proves same-host-path positional:romounts;sbx.shdoes not mount the per-sandbox host-config directory at/var/lib/acq/host. MSB already supports the required distinct destination. Guest copies, writable kit overlays, or guest-controlled symlinks are not acceptable because the agent has sudo. Architecture review is selecting either a real SBX mount capability or an explicitly versioned/backward-compatible contract evolution; no guessed flag or weakened trust boundary will be shipped.mogul commentedon Oct 21, 2026
🤖 Contract-v2 review disposition: Patterns #521 will define separate v1/v2 schemas and mandatory host validation, while production wiring remains here. #600/#606 acceptance must prove backend-owned read-only root enforcement, inject the neutral root for consumers, cross-check each materialized directory name against validated providerId/providerPath, distinguish root-not-ready from authoritative empty discovery, and exercise the real consumer path. These are tracked consumer obligations, not reasons to add a fake runtime consumer to the Patterns schema repository.
fix(provider-facts): preserve unset caller IFS (#605)
mogul commentedon Oct 21, 2026
🤖 Stack maintenance: the preserved projection WIP is now rebased onto current Quickstart
main, including merged #605. The restore conflict was limited toPATTERNS_KIT_REF; the merged fullv1.15.0SHAf3c6acb4d34a89b3b6539c44d47f56bacaeb94d7was retained. Projection implementation remains blocked on the reviewed/released v2 root contract in GSA-TTS/agentic-coding-patterns#522.mogul commentedon Oct 21, 2026
🤖 Adversarial review found commit-blocking defects in the initial projection WIP. Most importantly, fetching only the USAi kit cannot expose the released repository-level validator/schemas, so real manifests would fail. The implementation is being corrected to use a separately verified pinned control-plane checkout, per-sandbox locking, private atomic staging/rename, fail-closed backend mount setup, restored destructive-path guards, defense-in-depth provider target containment, and real command-shape/rollback tests. No unsafe partial implementation will be pushed.