Consumer integration
DA-REL-006 adds an inactive SDK artifact capability, not a private prerequisite workaround. Its trusted Node generator uses an existing immutable portable closure and data-only source descriptor. Exact private-source inventory and nested CI-docs manifest bytes remain bound; full archive/source qualification and any later operator eligibility decision remain independent prerequisites.
scripts/prepare-consumer.mjs installs the governed policy wrapper and patches
known workflow/validation boundaries. It preserves repository-owned commands.
scripts/onboard-changesets.mjs prepares selected public root packages for
version PRs; it does not publish them.
DA-INT-001 — Functional checks survive exemptions
Requirement. Trusted generated PRs MAY skip specification phases, but functional, audit, packaging and release gates MUST remain active.
Acceptance details
- Trust MUST use the PR author and bot type, not the actor rerunning a job.
- The configured dependency bot, Dependabot, Renovate and the existing generated version branch MAY qualify under the wrapper’s explicit rules.
- An aggregate specification command MUST still run configured functional lanes and propagate failures.
- Missing or untrusted context MUST retain ordinary specification checks.
DA-INT-002 — Version PR boundary
Requirement. Generated version workflows MUST use repository-scoped App writes and source-owned version preparation without publishing packages or creating GitHub releases.
Acceptance details
- Activation MUST remain explicit and checkout credentials MUST NOT persist.
- Version commands MUST retain source-specific metadata synchronization and CLI runtime requirements.
- Missing credentials MUST NOT silently substitute a workflow-token writer.
- Publication and signing MUST retain the owning repository’s approval boundary.
DA-INT-003 — Container context boundary
Requirement. Docker validation workers MUST receive only explicit public PR-context variables, never coordinator credentials.
Acceptance details
- Flat worker bundles MUST remain standalone; host coordination MUST attach the PR context before container creation.
- Unrelated Docker operations MUST remain unchanged.
- Integration MUST remain repeatable without duplicating policy imports or command wrappers.
DA-INT-004 — Update ownership
Preparation also repairs an existing untyped first-party ignore into explicit version-update types, retaining security updates rather than leaving a blanket suppression. Central operational drift reports missing/competing ownership and unknown security-setting coverage under DA-OPS-001.
Requirement. Consumer preparation MUST retain security coverage and avoid competing first-party version-update owners.
Acceptance details
- Dependabot security updates MUST remain enabled.
- First-party version-update ignores MAY prevent duplicate version PRs while the coordinator owns those scopes.
- Newly supplied PR pipelines MUST invoke the repository’s existing validation commands with read-only authority.
Versioning runtime qualification
DA-TOOL-001 governs the generated Node-only versioning contract. Onboarding preserves a supported existing CLI major and copies its exact runtime guard. Onboarding must refuse to overwrite a different source-owned version recipe; that consumer requires explicit source integration. The version-only template validates the installed CLI before App minting and does not install Deno. Notes’ separate frozen-host prerequisites remain owned by Notes; no consumer migration is implied by this upstream template correction.
The shared filesystem preparer preserves the immutable workspace file’s exact final newline sequence after validating the entire candidate. Native pnpm trimming cannot invalidate an otherwise unchanged source-owned version-input binding. No other candidate bytes are reformatted, consumer guard is weakened or new output path introduced beyond the already governed workspace input. The adapter canonicalizes its caller-owned workspace root once so platform path aliases do not misclassify ordinary files, while every descendant file and output parent must still resolve to its exact canonical path before any write.
The optional canonical-intake policy is data owned by each consumer. Shared rendering remains in the coordinator; an opted-in consumer verifies its actual candidate facts in an ordinary functional lane outside the trusted-PR spec wrapper. Main spec-first and functional/audit/release gates remain unchanged.
The workspace profile binds its complete selected importer set and explicit registry-transitive lock policy. It uses the same pinned shared preparer and branch-scoped target context, without executing a consumer hook. Every chapter must contain exactly one accurate source slot; stale facts, authored repairs, unexpected files and oversized output stop all canonical writes. Consumer adoption and the first genuine hosted candidate remain separate acceptance. Workspace slots preserve normal Markdown formatter output, including marker spacing and a bounded table-format directive, so a formatted adoption remains eligible for deterministic subsequent preparation without rewriting authorship.
DA-REL-004 requires complete package identity comparisons in both shared preparation and the owning offline adapter; version-prefix matches cannot normalize a different package version into an admitted development patch.
Independent development admission under DA-WAVE-007 grants no additional consumer commands or output paths. The existing offline source-owned guard and pinned shared preparer still qualify the full candidate; upstream publication waits, main specification-first and every functional lane retain their authority.
Schema2 intake preserves an already larger immutable source chapter only with non-growing line and byte counts, including for a no-op or genuine admitted patch. Both ordinary size bounds, exact source/policy/fact bindings, authored content, mapped owners and every independent source guard remain required; no consumer shim, arbitrary higher cap or generation-time exemption is added.
The filesystem preparer validates an optional changed schema1 maintenance note as a regular, bounded valid UTF-8 file before validating or writing canonical outputs. Only its exact branch-derived path and empty release metadata are admitted; the note itself is never a renderer output. All chapter and output parent checks still complete before any write, including on repeated preparation. Workspace digest paragraphs preserve exactly the immutable source’s one-line or two-line form; this adds no formatter execution, policy field, hook or output authority and leaves both profiles’ existing size and lock rules unchanged.
DA-WAVE-009 optionally isolates one explicitly granted Desktop development SDK view while retaining every other source update and constraint as deferred evidence. It requires the exact independent source descriptor/canonical guard, full current-source qualification and the separate artifact capability. Actual private-archive audits and candidate functional gates remain mandatory; the public tooling projection does not replace them or authorize runtime changes.