Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Overview and ownership

This repository is the LapisMD dependency coordinator. It discovers active first-party npm consumers, verifies registry availability and drives the existing Renovate runner. It also owns monitoring scope, workflow-authentication reports and the isolated organization-profile PR writer.

Canonical requirements live in this book. Source and tests prove their current implementation; README and the rollout plan explain operation and delivery. Rollout and remaining work separates deployed functions from planned dependency waves, operator UI, publication recovery and tooling work.

DA-OWN-001 — Source ownership

Requirement. The coordinator MUST own discovery, update policy and coordination while application behavior, package publication, signing and deployment authority remain with their owning repositories.

Acceptance details

  • First-party package defects MUST be fixed in the owning source repository and consumed through released registry ranges.
  • This coordinator MUST NOT publish npm packages or use package-signing credentials.
  • Consumer tests, audits, compatibility decisions and repository merge rules MUST remain effective.

System boundaries

OwnerResponsibility
Dependency automationDiscovery, stable-version eligibility, Renovate rules, release intent, notifications, monitoring policy, profile writer
Package repositoriesPackage behavior, tests, release decisions, provenance and publication
Lapis CIShared toolchain and dependency-image identity/provenance helpers
Lapis MaintenanceBrowser UI, live GitHub adapters, operator commands and session/cache boundaries
GitHubInstallations, encrypted secrets, checks, branch rules and deployment environments
npm registryAvailable published package versions and prerequisite metadata

The coordinator’s private npm workspace is tooling, not a publishable package. Its runtime is Node 24 with pinned pnpm. The specification validator is the Deno-free Node release. Some retained consumer-version templates still install Deno for Changesets 3; replacement remains explicit rollout work.

Repository policy

The default-empty config/scoped-admissions.json is a separate operator grant for DA-WAVE-009. Its exact Desktop descriptor, canonical-policy and immutable private-shape hashes do not enable another source or grant general private dependency updates. Every other source keeps ordinary whole-repository holds.

DA-REL-006’s separate artifact capability map defaults to no repositories. A source opt-in cannot enable native projections or alter any existing private, phase, CI, publication or audit hold. This implementation installs no live entry.

DA-PUB-005 registers only Agent UI’s reviewed tagged-workspace publisher and source-byte contract. It changes no repository phase, channel scope, publication floor, signing tool or completion authority.

The reviewed Notes channel cohort follows DA-PUB-003 with exact package, version, integrity and consumer-manifest scopes. It adds no repository entries and changes no phase, schedule or write activation. Profile’s separate reviewed consumer scope is restricted to Server’s root runtime dependencies; other Profile consumer scopes remain forbidden. DA-POL-001 through DA-POL-003 retain their existing authority and excluded hosts.

The November18 Notes refresh changes exactly four package identities to their verified source538bb469 cohort after same-byte publication recovery. It adds no consumer scope or repository and retains file-explorer0.2.8 and defaultlatest. Current-main qualification, source-owned canonical support and upstream floors remain independent holds; the normalized proof is recorded in spec/records/2026-11-18-notes-cohort-recovery.md.

The November19 identity-only refresh advances those same four pins to the current source2838c3dc cohort after exact-source release run44609414345: API0.6.10, UI0.2.6, Workspace0.4.9 and Profile0.2.7. It changes no consumer scope, repository phase, write setting, File Explorer pin or defaultlatest behavior. Exact cryptographic and prospective planning evidence is recorded in spec/records/2026-11-19-notes-channel-refresh.md; live writes and settlement remain independently gated.

The subsequent exact Server Profile scope changes only direct channel selection for its existing public prerequisite, as recorded in spec/records/2026-11-18-server-profile-scope.md; source compatibility, publication-floor and production audit holds remain independent.

Server joins the existing ten pilot entries after source103 and exact-main CI/image/Pages/completion qualification. Its measured empty managed note records no npm/private-package release intent; registry prerequisites, source intake, publication and production audit holds remain independent. Eligibility does not complete Server adoption or enable any excluded host.

config/repositories.json is the versioned authority for dependency-update entries, monitoring additions/exclusions and excluded package names. It is not a live installation or secret store.

The accepted initial rollout selected Notebook as the first pilot entry. With the coordinator phase retained at pilot, every full entry remains observation-only until its own adoption task explicitly promotes that entry. Existing completion callers remain read/dispatch observers independently of write activation. Excluded roots remain ineligible. A held full-phase source may register a separately reviewed metadata-only observer under DA-NOT-004; its hold and dependency-write ineligibility remain binding.

DA-POL-001 — Explicit dependency scope

Requirement. Dependency discovery and update targets MUST originate from validated repository entries with supported schema, unique identities and explicit rollout phases.

Acceptance details

  • Entries MUST identify a supported organization/account repository and pilot or full phase.
  • A supplied hold reason MUST be a non-empty string and MUST prevent that target from entering the write matrix.
  • Invalid or duplicate entries MUST fail before reconciliation.

DA-POL-002 — Monitoring authority separation

Requirement. Monitoring additions MUST expand read coverage without granting dependency-update or publication authority.

Acceptance details

  • Monitoring scope MUST be the sorted union of update entries and monitoring additions, minus monitoring exclusions.
  • Monitoring exclusions MUST win, and malformed or duplicate monitoring identities MUST fail validation.
  • Missing optional monitoring fields MUST retain legacy update-entry defaults.
  • Monitoring adapters MUST NOT mutate the dependency-write allowlist or remove holds.

DA-POL-003 — Excluded and held scope

Requirement. The rollout MUST preserve explicit repository/package exclusions and portable-leaf boundaries rather than activate parked Deno hosts or held consumers.

Acceptance details

  • Community and Nostr repositories MUST remain outside this rollout unless explicitly reauthorized.
  • Discovery MUST exclude parked Deno host paths, generated trees and fixtures.
  • Excluded package names MUST be ignored by generated Renovate rules.
  • An existing portable-leaf entry MUST NOT authorize its excluded service or host; retained excluded Deno roots MUST remain held in every rollout phase while their public metadata MAY remain read-only graph evidence.

Scope interpretation

Monitoring exclusions and update entries deliberately serve different purposes. For example, a repository may retain a portable package consumer entry while its service-oriented root remains excluded from broad monitoring. An explicit hold keeps a repository discoverable for explanation without making it writable.

AI Controller and AI Host retain explicit dependency-write holds in addition to their monitoring exclusions. Their existing entries continue supplying public prerequisite metadata; neither a future full phase nor later successful CI may turn those excluded roots into dependency-update targets.

Public operational coverage

The allowlist does not establish repository visibility. Discovery classifies visibility before collecting source. Public coordinator artifacts/state contain only verified public sources; inaccessible/non-public entries produce opaque coverage holds without widening credentials or revealing source names/bodies.

DA-INV-005 public raw reads use the same reviewed entries and exact source tree. They grant no additional installation, credential, private-source or write scope; unknown visibility and unverified file bytes remain held. DA-INV-006 HTTP diagnostics expose only sanitized failure context, never access tokens or bodies.

Monitoring token detection includes Changesets’ explicit github-token input; this classification does not expand dependency targets or installation scope. The separate config/tooling.json contract follows DA-TOOL-001 through DA-TOOL-003. Its repository-specific cohorts describe tooling rather than dependency edges or permissions. It cannot add advisory exceptions, change rollout phases, enable writes or activate excluded hosts.

Expanded tooling records may retain exact source/artifact hashes, resolved versions and historical successful source-CI context under DA-TOOL-004; that metadata never qualifies a whole version recipe or grants dependency writes. Reviewed source workflow/job selectors and package-manager provenance follow DA-TOOL-005/006; evidence refresh preserves existing supported tool ranges and retains undeclared manifests without inventing declarations.

The scheduled single-pilot checkpoint keeps global phase pilot, so only individually activated entries can enter the writer matrix. Its expected schedule value does not enable hosted scheduling: actual activation follows the selected pilot’s candidate/main/replay acceptance. Missing variables retain the workflow’s default-off gate, independently of checkpoint metadata.

config/operations.json records reviewed template references, single update class owners, retained exclusions and a dated activation checkpoint, without granting settings authority. config/advisories.json is the separately reviewed exact approval authority under DA-OPS-002; its initial list is empty. Source observations and raw audit findings cannot create approvals.

The initial November 16 operator decision added one exact coordinator deepmerge entry with the reviewed dependency-source/lock binding and November 21 expiry. This changes only advisory admission under DA-OPS-002; repository scope, existing holds, rollout phase and the separate write gate remain unchanged.

After retirement of that LOW decision, the November17 operator explicitly approves two exact HIGH picomatch runtime paths bound to dependency source 9d657a74 and lock SHA256a3e1f05f. Their exclusive November19,00:00UTC expiry and earlier known-fix termination are independent of the historical LOW scope. Only config/advisories.json grants those two tuples; all other findings, source/lock drift, stale approval cleanup and existing rollout gates still deny writes. The decision does not activate another repository or consumer exception.

Those two HIGH approvals are now retired after official upstream withdrawal and complete zero-finding audit evidence. Active approvals are empty again. This DA-OPS-002 cleanup neither installs a dependency fix nor grants any new exception; every future finding must pass the unchanged rejection policy.

Hosted activation observations may use the five values supplied by the trusted main audit workflow when its read token cannot query the Variables API. This read-only evidence follows DA-OPS-001; it cannot create defaults, change settings or grant writer authority.

Completion policy binds only existing pilot repository workflow IDs/paths and permitted source events. It adds no dependency write scope, removes no hold, and excludes the notification callback itself and the deferred Nostr publisher. Unknown or recreated workflow identities require explicit source review before notification adoption.

Publication policy reviews source-owned publisher workflow identities and exact verification-tool bytes under DA-PUB-001/002. It adds no update repositories, channel admission, source signing authority or publication permission.

Source-owned canonical intake is an optional preparation capability, not an activation or repository-scope change. Invalid policies fail closed; existing phase, portability, package exclusions and manual-repair holds remain binding.

Notebook is the sole additional pilot update entry for the bounded canonical Core development intake. This changes no global phase, schedule, service scope, package exclusions or held publisher. Source review and actual normal bot regeneration remain separate from source qualification of DA-WAVE-007; the bounded pilot runbook retains acceptance and rollback.

PR34’s explicit operator decision rebinds the single existing coordinator runtime LOW to source9d657a74 and locka3e1f05f…ca61b8b after the required validator update. This replaces the old exact tuple and preserves expiry, known-fix rejection and every other audit failure under DA-OPS-002. No write scope, activation setting, phase, package signing or deployment gate changes.

The five existing pilot tooling cohorts allow exactly spec-validator0.2.0 or the reviewed Deno-free0.2.1 patch. This explicit DA-TOOL-003 policy repair unblocks the source-owned release-intent hook without skipping it or widening other tooling families. Historical source/lock evidence remains unchanged.

The same exact advisory entry is now retired after official upstream withdrawal and complete zero-finding audit evidence. Active approvals are empty. This DA-OPS-002 cleanup neither installs a dependency fix nor grants any new exception; every future finding must pass the unchanged rejection policy.

Docs and Tasks add exact completion observation and one-repository read-only App readiness targets while retaining source phase full until separately reviewed activation. This metadata does not grant writer, publication or audit-exception authority. Their earlier HIGH Changesets finding cleared after upstream advisory withdrawal; only separately qualified source adoption may precede a reviewed phase change.

The next small-repository slice registers Spec Validator’s existing Check workflow and Visual Delta’s existing CI, PR-specification, Pages and version workflows by exact IDs, paths and supported events. The read-only App probe adds only those two exact targets. Tag publishers, native capture, image publishers and callback self-triggers are not completion sources; verified npm notifications remain separate. Registration74 initially retained phase full for both repositories pending merged source acceptance and separate activation/replay, now recorded below. Spec Validator currently consumes no Lapis npm dependency; no synthetic Core pin or version recipe is introduced to create an update. Visual Delta consumes only the Deno-free specification tool in development and retains its existing audit and compare-only browser gates. The operator requests a final merge pass and gives standing approval for per-repository activation after passing source acceptance; advisory exceptions and global full rollout are not implied.

The operator-approved next activation adds only Spec Validator after its source7 mergedf3bab11837648045540bf7ef948503131dcab041 and main Check44174151693 passed. Read-only existing-App probe44173967888 passed. Its normal functional no-Lapis-input contract preserves the current zero-update graph; no Changesets writer, dependency bump, version/tag or publication is invented. Notebook remains the sole exercised dependency-writing consumer; all other entries and existing holds/exclusions remain unchanged, and global phase stays pilot. Actual completion, ordinary no-update settlement and repeat receipts are recorded in the source activation record; source registration alone is not claimed as a new publisher or multi-consumer update proof.

Visual Delta adoption79 and activation77 are deployed after current source acceptance. Ordinary runs44182784733 and44182833366 qualify e755e2a0 with no updates, holds or waits, retain the same unchanged operation and form the verified durable state chain178→179. Exact source, Pages, artifact and state receipts are in the activation record. Notebook, Spec Validator, Visual Delta, Terminal and Registry are the pilot entries; other entries, exclusions, global phase and holds remain unchanged. Visual Delta’s independent guard admits only compatible Node-only validator0.2 development patches. No new dependency update or publisher execution is claimed.

VD-GOV-008 continues to gate audit remediation and package publication. The earlier blanket maintenance hold was too broad; the existing unapproved HIGH remains a publication blocker. This adoption does not change audit collectors, waive a finding, rebind an exception or authorize tags, uploads or baselines.

Parallel rollout and explicit Deno-package exclusion

The next adoption batches cover existing Node foundations/plugins, native/server packages and applications/registry independently. Only the parent coordinator changes registrations, per-repository activation or durable shared state; source preparation does not enable writes. Notebook, Spec Validator and Visual Delta were the three enabled entries at the start of parallel preparation; subsequent per-entry activation is recorded in the dated sections below.

Agent Redaction publicly exports ./deno and requires pnpm test:deno under its tracked guide. The operator excludes any Deno package. Its monitoring exclusion, package ignore and explicit dependency-write hold therefore preserve graph observation without adopting, porting or activating that source. This excludes adoption64 rather than claiming successful Node-only acceptance. Community, Nostr and every prior frozen host exclusion remain unchanged.

Terminal and Registry activation

The operator’s standing post-merge approval promotes only Terminal and Registry from full to pilot after their current source/main/callback acceptance. All other phases, global pilot settings, exclusions, source holds and advisory bindings are unchanged. Exact evidence belongs in the activation record.

Terminal source27 merged50d1bb9f with qualified macOS CI, spec Pages and actual false version intent. Its independent Core0.13 development-patch guard qualifies the real released0.13.4→0.13.5 candidate, including the no-note full version recipe; the coordinator’s empty-Changeset flag remains unchanged. Registry source184 merged69d8c063, passes current Checks/signed publication and actual callbacks, and retains its private API0.1/no-version contract. Its upstream API publication wait remains binding; activation does not waive that prerequisite or claim an invented npm release. Ordinary live settlement and replay are required after policy deployment.

The Desktop observer registration names only CI400533153 and Pages403244157, with their exact paths and original PR/push/manual events. Its explicit heldObservers opt-in is valid only while the existing private/archive hold and full phase remain present. It grants no writer admission, publication authority, private registry access or version recipe; a later promotion must remove this observer opt-in rather than silently inherit it. Excluded Deno roots cannot use this registration mechanism. Schedule, preview, trial, health, image publication and callback self-triggers remain outside the allowed workflow/event pairs.

Plugins and Agent UI activation

The operator’s standing post-merge approval promotes only Plugins and Agent UI from full to pilot after exact-source, current-main and verified completion acceptance. Their existing empty-Changeset settings stay unchanged: each real version recipe correctly returns false intent without a forced empty note. All other phases, holds, exclusions, global pilot settings and exact advisory bindings remain unchanged. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; unavailable upstream publication floors are not waived, and no dependency update, version PR or publication is invented to force activity.

AI and JJ Store activation eligibility

Standing post-merge operator approval promotes only AI and JJ Store from full to pilot after independently green source adoption and whole-recipe acceptance. Both entries add the proven emptyChangeset: true capability: an actual managed empty note lets the source CLI classify supported development intake without inventing version or publication intent. Their real no-note macros alone do not prove the changed-candidate guard succeeds. The bounded activation receipt retains those separate controls and exact current-main observations.

This is eligibility, not a current-main qualification override. Pending or failed current CI, source/audit policy, ownership and publication prerequisites still hold actual writes and release-chain advancement. Existing seven pilot entries, every other empty-note setting, exclusions, holds and global pilot gates remain unchanged. Ordinary live reconciliation, exact settlement and repeat acceptance remain open until their own receipts exist. The user’s unrelated JJ Store main/release repair exclusion does not alter the collector or assert a pass.

Notes activation eligibility

Standing post-merge operator approval promotes only Notes from full to pilot after source155 merged with all required checks passing. Its existing measured emptyChangeset: true flag remains unchanged. Source policy limits supported inputs and preserves frozen hosts; publisher/channel/audit authority stays with the source. The activation record separates source acceptance, current-source release preparation and the live publication attempt. Pending current CI and upstream/publication waits continue to hold writers. Existing nine pilot entries, all other flags/holds/exclusions, empty artifact capabilities and global pilot/schedule settings are unchanged. Actual publication proof, ordinary live settlement and repeat remain required; policy eligibility alone does not complete adoption53.

Mira, Design Core, Tasks and Docs activation

Standing post-merge operator approval promotes only Mira, Design Core, Tasks and Docs from full to pilot after independently green source adoption, current-main checks and verified completion callbacks. Mira retains its existing emptyChangeset: true flag; the other three introduce no forced empty note. Desktop’s private-archive holdReason, every Deno/community/Nostr exclusion, every other phase/flag and global pilot settings remain unchanged. Active advisory approvals stay empty after the picomatch retirement. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; retained branch-ownership holds and upstream publication waits are not waived, and no dependency update, version PR or publication is invented to force activity.

Inventory and registry availability

DA-REL-006 discovers only a bounded data-only artifact descriptor and its exact immutable inputs. Discovery grants no operator capability or private-scope admission; an absent central capability retains normal held behavior.

Public source opt-ins retain their bounded original declarative policy bytes beside the parsed policy and digest at the exact discovered revision. Independent canonical development admission verifies their agreement; older inventory without those bytes remains held until fresh discovery. This adds no private coverage, executable source authority or Maintenance/durable report fields.

src/github.mjs performs authenticated GitHub GETs and public registry reads. src/policy.mjs selects active manifests, resolves catalog ranges, discovers runtime cycles and computes eligible stable versions. scripts/inventory.mjs writes ignored local reports and a gated reconciliation matrix.

Manual empty-attempt recovery may read complete immutable public trees at the originating and explicitly selected current source revisions. A source advance qualifies only when every non-operational blob/commit identity and mode remain equal; documentary/workflow/version-guard/test changes cannot conceal a changed manifest, lockfile, workspace, canonical intake policy or implementation. Unknown or truncated trees remain holds before state publication or consumer writes.

Manual partial-operation reconciliation uses current inventory facts rather than immutable-tree recovery projection. It requires the exact stored operation, state revision and completed originating run, then accepts only qualified advanced public source with complete empty branch/PR/orphan evidence. Inventory records the strict already-satisfied/remaining target partition before ordinary planning independently decides whether a new matrix entry exists.

DA-INV-001 — Revision-bound discovery

Requirement. Inventory MUST discover active workspace manifests at an exact source revision and retain ownership, consumer and portability evidence.

Acceptance details

  • The default branch commit MUST be resolved before tree/file reads; explicit notification revisions MAY select a particular source commit for hint verification only; the production graph MUST use current default branches.
  • Truncated trees, missing root manifests and duplicate public package owners MUST fail discovery.
  • Workspace includes/excludes and catalogs MUST determine active first-party dependency edges.
  • Private application manifests MAY be consumers but MUST NOT become public package owners.

DA-INV-002 — Registry authority

Requirement. Registry metadata MUST determine available stable versions; notification payloads MUST NOT authorize a version that the registry cannot qualify.

Acceptance details

  • Only HTTP 404 MAY mean unpublished; other registry failures MUST fail the scan.
  • Candidates MUST be stable, non-deprecated and no newer than a valid stable latest tag.
  • First-party runtime and required peer prerequisites MUST be available recursively until the candidate set converges.
  • An optional first-party peer MAY be absent without excluding the candidate.

DA-INV-003 — Portable target eligibility

Requirement. Inventory MUST withhold reconciliation targets whose source cannot support a portable registry update.

Acceptance details

  • First-party link: or file: dependencies and unpublished external prerequisites MUST hold the consumer.
  • Required Changesets onboarding and explicit holds MUST be satisfied before inclusion in the matrix.
  • The selected rollout phase MUST restrict the matrix, and each consumer MUST pin an exact pnpm version.
  • Reports MUST retain blocked reasons rather than describe held consumers as healthy writable targets.

DA-INV-004 — Runtime cycle discovery

Requirement. Inventory MUST identify runtime strongly connected components so already-compatible cyclic dependencies can avoid repeated release bumps.

Acceptance details

  • Runtime and optional-runtime edges MUST participate, including internal workspace edges.
  • Components with multiple members or a self-edge MUST be reported deterministically.
  • Cycle-aware rules MUST use lockfile updates for applicable compatible runtime ranges.

DA-INV-005 — Bounded public source transport

Requirement. Production inventory MUST bind credential-free public source-file reads to the exact Git tree while avoiding file-by-file GitHub API quota.

Acceptance details

  • Public visibility, an immutable source revision and the requested tree blob identity MUST be verified before reading source bytes.
  • Exact raw bytes MUST reproduce the Git blob SHA; unsafe coordinates, redirects, HTTP failures, oversized responses and mismatches MUST hold discovery without an API fallback.
  • Each response MUST retain a 4 MiB bound and 30-second timeout; each repository reader MUST cap requests at256 files and total bytes at16 MiB, without authorization credentials.
  • Repeated reads MAY reuse only an invocation-local result for the same revision/path; registry and publication-proof budgets MUST remain unchanged.

DA-INV-006 — Sanitized HTTP failure context

Requirement. HTTP failures MUST retain bounded diagnostic status and quota context without exposing credentials or response bodies.

Acceptance details

  • Confirmed quota exhaustion MUST remain distinct from an unclassified permission or HTTP failure.
  • Diagnostics MAY retain origin/path, numeric quota/reset/retry values and a bounded request identity; URL credentials, query strings, authorization and response bodies MUST NOT be retained.
  • Diagnostics MUST NOT add retries, grant permissions, suppress failed evidence or admit writes.

Operational reports

Before planning writable waves, inventory audits the frozen coordinator graph under DA-OPS-002/003. Denied qualification retains read-only observations but plans with writes disabled and emits no writable target matrix. State-only pilot reporting remains separately gated and available.

The report contains schemaVersion, exact repository source revisions, manifests, package owners, consumer edges, cycles, eligible versions and unpublished names. These operational reports remain under ignored reports/ and Actions artifacts; the public specification site does not embed them.

Wave mode additionally reads pnpm lock importers at the exact tree revision via Git blobs (including large lockfiles), registry integrity/dependency contracts, and complete current workflow/check/status evidence. Missing lock or observation coverage remains explicit. Flat mode retains its existing discovery contract.

Qualification collects push and PR workflow contracts separately and observes all current workflow runs/checks/statuses. Branch evidence retains PR/commit authors, exact ancestry and candidate lock data; rerun actors are not owners.

Workflow expectations honor exact changed-path and default-branch trigger filters; non-triggering image/deployment workflows are not invented missing checks, while unknown path coverage remains fail-closed and every observed current workflow still participates in qualification.

Tooling observations follow DA-TOOL-002. Production discovery includes root lock evidence and records the exact source SHA with cohort findings. Those observations neither add update targets nor turn missing evidence into success. Reviewed Node CLI bytes remain distinct from whole-recipe capability. Root Deno formatter declarations are reported as requiring source qualification, not proof that a generic Node-only contract may replace an existing runtime.

Tooling discovery additionally hashes the exact root manifest and lockfile bytes under DA-TOOL-004, so historical cohort CI context remains visibly distinct from changed current source/artifacts and unqualified version recipes.

Completion callbacks settle before the full inventory starts under DA-WAVE-005. Their PR head revisions are verified independently and never passed as graph discovery overrides.

Current public owned versions remain in normalized registry observations even outside latest eligibility under DA-PUB-001/002. Optional-runtime contracts are retained alongside runtime/peer metadata. Production wave inventory collects bounded authenticated public publication evidence; flat selection and the latest-only candidate closure remain unchanged.

Publication artifact reads reuse the existing contents-read workflow token for explicitly public repositories. Inventory requests no App credentials or extra permissions. Missing artifact-read access remains an explicit publication hold; it does not justify widening access automatically.

Canonical-intake opt-ins are bounded declarative JSON read at the exact admitted default-branch source. Their immutable digest and exact chapter paths accompany configuration; no candidate policy or executable module can widen write paths.

Wave inventories retain the unpruned stable candidate pool and a source-policy digest for reviewed channel projection. The normal available pool remains latest-only; path-specific prerequisite closure cannot widen another consumer.

DA-WAVE-009 retains structured originating unpublished/local-path findings beside the existing human constraints. Fresh exact-target discovery reconstructs the same unpublished findings from immutable source and observed registry absence before replanning; matching text cannot grant scope authority. Human summaries retain selected SDK scope and deferred update/hold/wait counts.

Reconciliation and review policy

DA-REL-006 may select only an explicitly operator-enabled source SDK regex profile. Its existing trusted post-upgrade command owns native seeded artifacts; ordinary npm management, default artifact checks, admission holds and write gates remain unchanged. No live Desktop capability entry is supplied here.

The runner uses generated central rules, not consumer-controlled Renovate configuration. scripts/configure-renovate.mjs selects a target only from the validated inventory. renovate.config.cjs binds that generated configuration, the single allowed post-upgrade command and explicit write activation.

Canonical opt-ins retain the exact governed pnpm-workspace.yaml path alongside their exact chapter paths in native post-upgrade artifact filters. This allows the validated filesystem repair to replace native package-file bytes in the final commit. Ordinary sources retain only the deterministic Changeset filter; no manifest, source-code or broad specification wildcard is added. The workspace remains subject to the complete source-owned semantic/scope validation.

Manual recovery binds the exact stored operation, completed originating run, current state revision and empty dependency branch/PR evidence. If source has advanced, a separate exact current-source input and immutable-tree projection must prove unchanged non-operational code/inputs. This only records recovery; fresh ordinary planning, source revalidation and every writer/merge gate still apply. No repair branch or live state is overwritten to resume an old attempt.

Manual partial-operation reconciliation is distinct from recovery. It binds the exact admitted operation, completed originating run and current state revision, requires qualified advanced public source with empty dependency branch/PR/orphan evidence, and records only a strict target partition already proven by ordinary manifest, retained-minimum, peer and lock facts. Fresh planning must independently admit the remaining targets before the App writer runs; the reconciliation input cannot select or widen their generated update.

DA-REC-001 — Restricted update managers

Requirement. Generated reconciliation MUST handle only eligible first-party npm dependencies within discovered active manifest paths.

Acceptance details

  • All packages MUST start disabled; only the first-party npm scopes MAY be enabled.
  • Own packages, excluded packages and unpublished or prerequisite-ineligible versions MUST be ignored or disabled.
  • Existing exact/caret/tilde styles and peer support MUST be retained, with widening only when the candidate falls outside support.
  • Consumer-local Renovate settings MUST NOT override central target restrictions.

DA-REC-002 — Compatible and breaking reviews

Requirement. Compatible updates MAY auto-merge only after checks succeed and repository rules permit; major and pre-1.0 minor updates MUST remain separate compatibility drafts.

Acceptance details

  • Compatible changes MUST use one grouped rolling PR per consumer.
  • Breaking families MUST disable auto-merge and remain draft PRs.
  • Native platform auto-merge and ignored tests MUST remain disabled; stale branches MUST be refreshed.
  • Existing review/merge requirements MUST NOT be bypassed or replaced with manufactured approvals.

DA-REC-003 — Explicit write activation

Requirement. Reconciliation MUST default to pilot dry-run and require explicit operator activation before repository writes or broader rollout.

Acceptance details

  • Only LAPIS_DEPENDENCY_WRITES=true MAY enable writes; unset values MUST select full dry-run.
  • Full phase MUST require LAPIS_DEPENDENCY_PHASE=full; other values MUST retain pilot selection.
  • Scheduled scans MUST require LAPIS_DEPENDENCY_SCHEDULE=true; manual diagnosis MUST remain available.
  • Writable planning and App minting MUST pass the actual coordinator advisory preflight, with App key and bot author additionally required before writable reconciliation.

DA-REC-004 — Constrained execution

Requirement. The runner MUST constrain post-upgrade execution and credentials to the reviewed coordinator contract.

Acceptance details

  • Tokens MUST be minted for one selected repository with contents/PR writes and checks/status reads.
  • The only allowed post-upgrade command MUST be the exact coordinator prepare-pr.mjs entrypoint with source-bound workspace context and output paths.
  • General package scripts and unrestricted environment exposure MUST remain disabled.
  • Reconciliation MUST NOT prune stale branches automatically; wave mode adds explicit repair ownership.

Native artifact reporting

Native artifact-error status writes MUST be disabled for the status-read-only token. Preparation errors MUST retain native PR reporting and functional CI/merge gates rather than require additional status-write authority.

DA-REC-005 — Native review context

Requirement. Generated dependency PR notes MUST add bounded, escaped, public-source review context through Renovate’s native prBodyNotes, preserving its package table, release notes, configuration, controls and metadata.

Acceptance details

  • Context MUST identify the exact consumer source and available wave observation/policy revision, discovered paths, compatibility and release-intent policy without claiming that earlier CI qualifies a later PR head.
  • Candidates and holds MUST be labelled as repository scan evidence, not the current PR diff; incomplete or absent wave/CI evidence MUST remain explicit.
  • The native rebase/retry checkbox MUST retain its native marker and meaning, with the next eligible coordinator run respecting source/manual-repair holds, current-head CI and repository protections; no unwired action checkbox MAY be added.
  • Updating an existing body MUST replace only one well-formed Lapis-managed section or the exact legacy Lapis note, leaving native bytes and maintainer additions intact; ambiguous sections MUST stop the update.

Wave scheduling boundary

The default flat matrix remains the rollback path. Explicit wave mode selects only admitted consumers and restricts generated versions to their admitted candidate set. Durable admission precedes writable consumer execution; current source/repair ownership is read again before invoking Renovate. See waves.

Wave-mode auto-merge additionally requires complete current PR-head workflow coverage, an exact already-qualified candidate and current source ancestry. Revalidation refreshes the inventory before generating executable rules. A new or regenerated head waits for its own CI rather than inheriting an earlier green head. Closed breaking-family branches hold that family; compatible work in a different family remains eligible. Workspace catalogs move only with all their references jointly admitted, including preservation of peer support.

Compound runtime support follows DA-WAVE-006: per-path native lockfile rules preserve existing support while exact candidate lock and CI evidence continue to gate auto-merge.

Wave inventory prepares the exact reviewed standard provenance-verifier CLI through the owned pinned setup action. Verification remains a read-only publication-evidence gate and never broadens the latest-only candidate policy.

Public publication collection reuses inventory’s existing contents-read workflow token. It has no App credentials or new permissions and cannot replace separate state/write admission. Unavailable artifact access leaves evidence unknown.

Opted-in canonical preparation extends post-upgrade file filters with only its reviewed exact chapter paths. The runner still executes only the shared preparation command, with lifecycle scripts disabled and manual branches held. When its single-development profile independently qualifies, the exact matching pnpm-workspace.overrides edge MUST be admitted alongside the root development dependency at the same target. This does not enable peer/runtime edges, another workspace file, compound selectors, catalogs or other overrides.

DA-PUB-003 channel targets use exact admitted path/type/version rules with respectLatest: false only on those individually approved rules. Default and flat configuration retain latest protection, breaking drafts and all CI gates.

DA-WAVE-009 carries an explicit exact scope binding through generated context and rejects missing or revoked authority before artifact copyback. Dependency PR context labels SDK-only selection and preserves bounded deferred Core/private constraints; it must not describe selected admission as full-source acceptance. An unrelated PR is not evidence of an uncertain target write. Exact owned branch/candidate manifest-lock coverage remains required before normal replay.

Dependency and release waves

DA-WAVE-009 is an inactive, separately granted SDK-only selected view. The artifact-generation opt-in alone does not waive any source admission hold.

DA-PUB-005 may retire an Agent UI publication wait only after exact tagged-cohort verification; its source publisher and main-only completion gates remain distinct.

The schema2 workspace canonical capability applies to ordinary admitted compatible patches across explicitly covered manifests. It verifies source policy bytes, active importer coverage, current locked facts and exact registry targets before writer admission. A wait on the selected dependency remains binding, but a wait on a different dependency MUST NOT contaminate a complete policy-mapped edge merely because both share one manifest; the unrelated wait remains visible and continues to block its own update. Only the existing schema1 development profile retains the broader separately bounded independent-wait behavior.

Wave admission is implemented behind LAPIS_DEPENDENCY_WAVES=true, default off. Hosted pilot qualification and activation remain separate operator decisions.

The reviewed configured Profile publication binding retires only its own genuinely newer, fully verified and currently qualified release. Direct Profile selection is separately restricted to Server’s root runtime dependency scope; that scope cannot bypass source compatibility, dependency floors, channel drift or replay/CAS gates, and does not admit another Profile consumer.

An existing waiting release intent MUST retain an actionable direct runtime or optional-runtime manifest-minimum repair when a compatible simple caret/tilde range still starts below its exact required target, even if an incidental lock refresh already installed that same currently eligible target. Only the same public package/repository/field intent qualifies. Missing or settled intent, private packages, peers, development fields, catalogs, compound/custom ranges, changed targets and newer installed versions MUST NOT create this repair. The ordinary candidate, source/ownership/rollout and newer verified publication-floor gates remain required; no release wait is cleared from a lock update alone. An unobserved admitted operation MUST remain uncertain across unrelated source changes until both its retained minimum and lock target are observed on main; a newer source SHA and matching lock alone MUST NOT assert completion. Independent channel/provenance publication holds MUST remain visible while a retained manifest-minimum repair is actionable; their visibility alone does not authorize a downstream update or suppress an eligible upstream repair.

The exact November18 Notes cohort refresh retires only freshly verified publication/channel waits under the existing scoped contract; current-main CI, upstream dependency floors and source-owned intake remain binding. Origin and recovery attempts retain the same artifact identity, without a new operation or synthetic publication.

The November19 identity refresh advances those same four scoped Notes pins to the exact current publisher source and attempt3-verified artifact. Wave planning may use API0.6.10, UI0.2.6 and Workspace0.4.9 only on their pre-existing paths, and Profile0.2.7 only for Server’s root runtime scope. File Explorer0.2.8, default latest, all scopes and independent waits remain unchanged. A read-only projection may prove Server admission, but only merged-source reconciliation can create its actual operation and writer target.

Canonical schema2 preparation checks target availability through the same exact repository/path/dependency-type reviewed channel projection as wave planning. Raw latest-only availability stays unchanged; valid scoped next patches do not become unsupported solely because they are absent from that raw pool. It may isolate an otherwise complete selected edge from an unrelated package’s same-manifest wait without deleting that wait. A selected-dependency wait, current source qualification and every other admission gate remain binding.

DA-WAVE-001 — Derived admission

Requirement. Wave admission MUST derive update and public release chains from exact manifest, lockfile and registry evidence before selecting consumer targets.

Acceptance details

  • Runtime, optional-runtime and peer changes use the existing release-intent contract; dev-only updates do not create publication waits.
  • Every required publisher must qualify and publish a newer registry version carrying the intended dependency contract before its downstream wave proceeds.
  • Explicit holds, excluded packages, unknown locks, unavailable prerequisites and cyclic release chains remain visible and fail closed.
  • Package/path admission MUST move catalog references jointly while retaining the existing compatible rolling PR and breaking-family drafts.

DA-WAVE-002 — Durable reconciliation

Source-advanced recovery requires an operator-supplied exact current SHA and complete public trees at both immutable revisions. Only regular documentation, workflow, version-guard configuration and test blobs may differ; package, lockfile, workspace, policy and implementation changes reject recovery. Truncation, unavailable trees, duplicate/unsafe paths, changed symlinks and missing source bindings fail closed. Recovery records both revisions and the unchanged projection digest; fresh normal admission still owns target scope. Reports remain ignored artifacts; no live state enters main or public book output.

Partially absorbed operation reconciliation is a separate manual decision, not source-advanced empty recovery. It requires an exact stored operation and state revision, its completed originating run, qualified advanced public source and proven empty dependency branch, PR and orphan state. The ordinary retained minimum, peer-support and lock predicates MUST divide the old targets into a strict nonempty absorbed subset and a strict nonempty remaining subset. The partition and current source are durable state evidence; fresh ordinary planning alone may admit the remaining targets. None/all partitions, stale state, unqualified source and repair ownership MUST reject without changing state.

Requirement. Versioned wave state MUST reconcile registry observations, source revisions and operation identities independently of notification delivery order.

An unrelated observed PR MUST NOT clear an uncertain operation. Each retained target requires bot-owned branch-family and exact public candidate-head evidence covering its manifest/lock tuple; missing candidate data and empty historic targets remain uncertain until explicit recovery. A later compatible candidate may cover an older target without relaxing minimum or peer-support requirements. Candidate observation MUST evaluate resolved targets through the same exact repository/path/dependency-type reviewed channel projection that admitted the operation. Raw latest availability cannot strand a genuine scoped-channel PR, while stale, forged or out-of-scope channel evidence remains unobserved. A failed candidate may prove that the writer created the owned branch without qualifying that head for merge. The state writer MUST record that exact observation before a new operation may rewrite the rolling dependency PR, so the later head cannot erase evidence for the older operation or resurrect its uncertainty. Ordinary retry, current-head CI and merge gates still apply.

For state written by an older planner that admitted the successor without the new receipt, a different same-repository operation with a strictly later writer run is itself durable proof that the older operation passed observation: the planner cannot assign that later run while an unobserved earlier operation is unresolved. This backfill MUST require both stored run identities, MUST NOT infer from planned or held operations without a writer run, and grants only the same observed-on-branch outcome.

Public reports MAY include a bounded presentation-only attention projection derived from existing holds, waits, qualification and ownership evidence. Each entry retains a stable category, remediation and validated public coordinates without granting command authority or replacing immutable evidence. The projection MUST be derived only after the node’s current status and holds are final, including unresolved-operation detection. A published package awaiting reviewed-channel admission or an unreviewed publisher contract MUST remain distinguishable from a missing publication and MUST NOT instruct an operator to publish the same bytes again.

Acceptance details

  • Registry-verified version/integrity identities coalesce duplicate hints; complete scheduled scans recover missed events without treating payloads as authority.
  • Persistent operations retain exact targets, source/policy revisions, publication baselines and blocked/failed/uncertain outcomes for future operator UI use.
  • State lives only on the dedicated coordinator state branch, with optimistic concurrency and read-back after uncertain writes; conflicting state is never overwritten or blindly retried.
  • Exact manual recovery MAY re-admit only a completed originating run with proven empty branch/PR state and unchanged public source or an explicitly bound current revision with complete immutable-tree proof of unchanged implementation and dependency inputs; separate exact manual operation reconciliation MAY terminally partition only a completed empty admission whose qualified advanced source already satisfies a strict subset of its targets, without classifying changed inputs as unchanged recovery or directly granting the remaining writer operation.

DA-WAVE-003 — Qualification and repair ownership

The accepted initial single-repository pilot selected Notebook in source pilot phase. Other consumers remain observable, including through already deployed verified completion callers, but cannot enter the pilot writer matrix. Enabling the schedule does not promote full entries or bypass candidate/ownership checks.

The next standalone-plugin wave prepares Docs/Tasks completion observation without changing those writer phases. Their source-owned full-audit gates previously reported an unapproved HIGH Changesets/picomatch finding; that advisory was withdrawn upstream and fresh consumer audits are clean. The retired coordinator-only runtime approval never authorized consumer findings.

Requirement. Reconciliation MUST preserve manually repaired branches and require complete current revision qualification before advancing release chains.

Acceptance details

  • Repair/orphan holds MUST apply to their exact rolling or publisher compatibility family while ambiguous history remains held.
  • Genuine PR creators and every branch commit author MUST establish ownership independently of rerun actors.
  • Auto-merge MUST require complete current workflow/check/status qualification for the exact existing candidate on current source, with default-branch qualification evaluating the latest run for every active push workflow and independent external checks/statuses while manual, scheduled or otherwise non-expected GitHub Actions runs on the same commit remain visible operational evidence without falsely changing that push qualification.
  • Per-consumer failures MUST retain independent progress without weakening product, audit, publication or compatibility gates.

DA-WAVE-004 — Gated workflow integration

Requirement. The production reconcile matrix and generated allowed versions MUST enforce wave admission only under explicit rollout and state-write gates.

Acceptance details

  • Default-off wave mode preserves the existing flat reconciliation rollback path and pending state.
  • Trusted-main state publication uses a separate contents-write job scoped to the coordinator; consumer credentials remain per repository and cross-account installations remain separate.
  • Writable wave reconciliation requires successful durable admission before consumer writes, then fresh per-target source/ownership validation immediately before execution.
  • Hourly/manual/publication reconciliation provides recovery without activating settings, publishing packages or modifying protections.

Public operational storage

Public storage contains only explicitly public repository coordinates. Unavailable or non-public source coverage is held and represented by opaque IDs/counts; public repository artifacts and the state branch are not private storage.

DA-PUB-004 supplies a separate bounded static-plugin batch profile for genuine multi-package publication evidence. The selected package still requires its authenticated provenance, exact artifact digest, signed bundle and published-byte agreement before downstream admission. Archive-size holds remain explicit; the profile does not waive current-source checks, publication prerequisites, channel restrictions, ownership or operation CAS. The full-inventory collector uses the shared 128 MiB/256-request resource gate and observes all current owned versions before other tag/baseline probes. Reject-only claim preflight and the static verifier’s 16 MiB npm cap do not qualify a publisher or alter release floors; incomplete or oversized publication evidence remains held even when its download fits the total budget. The atomic state commit also includes public-safe report.json, consumed by Maintenance through GitHub Contents at the branch’s immutable revision.

DA-WAVE-005 — Completion timing and source isolation

Requirement. Completion-triggered reconciliation MUST settle the exact notifying callback before observing qualification and MUST retain default-branch graph authority.

Acceptance details

  • The receiver MUST validate the public source and callback workflow/run/attempt identity, then wait read-only for successful run and exact check-suite completion with a bounded explicit failure rather than silently accepting pending or unknown evidence.
  • The callback’s own current check MUST remain part of existing qualification; no product, audit, deployment or compatibility lane may be exempted to avoid a notification race.
  • PR-head hints MUST NOT replace the default-branch inventory, select unmerged dependency targets or assert qualification; duplicate and stale arrivals MUST remain ordinary authoritative scans.
  • Manual scans and gated scheduled recovery MUST remain available for missed events or failed callback settlement without changing rollout settings.

DA-WAVE-006 — Compound support ranges

Requirement. Admitted compound runtime ranges MUST preserve their supported release lines while qualifying their exact lockfile update.

Acceptance details

  • Targets already inside a compound support range MUST retain that range and use native update-lockfile rules for the admitted path and dependency type.
  • Targets outside compound support MUST remain held for source-owned compatibility review rather than silently narrowing the public contract.
  • The exact existing candidate MUST resolve the admitted target under the preserved range and pass its own current CI before auto-merge.
  • Earlier compound publication waits MAY be superseded only after qualified current main locks satisfy every target under identical registry-verified published support; a genuinely newer mixed release MAY retain that same compound-lock evidence only when all remaining ordinary/peer publication floors also pass, without claiming a new publication for compound-only retirement.

Publication evidence boundary

DA-PUB-001/002 separate authenticated publication facts from latest-only update eligibility, with only the explicit DA-PUB-003 cohort exception. Waiting releases expose channel-not-admitted/provenance-unknown without relaxing newer-version, compound-support, current-main or CAS rules. Legacy publication records remain readable; fresh receipt/channel evidence owns any new release advancement.

Reviewed channel projections retain default stable availability and apply only to exact active consumer scopes. Release retirement still requires the same newer-version/floor or identical compound-contract proof, current qualification, operation identities and CAS; an approved channel is never a release or CI waiver.

DA-WAVE-007 — Independent canonical development intake

Requirement. A source-opted-in compatible development patch MAY advance independently of unrelated publication waits only within its exact canonical preparation contract; every other hold and wait MUST remain binding.

Acceptance details

  • Admission MUST verify immutable source policy bytes/digest and exact existing development, override and lock facts for one policy-named forward patch with no release intent.
  • Missing or changed evidence, additional targets, catalogs, runtime coupling and peers needing changes MUST remain held under ordinary registry/channel eligibility.
  • A wait for the selected dependency MUST still block it while unrelated waits MUST remain visible and block their own updates.
  • Complete current source qualification, rollout scope, ownership, cycles, optimistic concurrency and frozen candidate/canonical-lock validation MUST remain required without widening public contracts or clearing publication evidence.

DA-WAVE-008 — Source preparation before writer admission

The next small-repository slice registers Spec Validator’s existing Check workflow and Visual Delta’s existing CI, PR-specification, Pages and version workflows by exact IDs, paths and supported events. The read-only App probe adds only those two exact targets. Tag publishers, native capture, image publishers and callback self-triggers are not completion sources; verified npm notifications remain separate. Registration74 initially retained phase full for both repositories pending merged source acceptance and separate activation/replay, now recorded below. Spec Validator currently consumes no Lapis npm dependency; no synthetic Core pin or version recipe is introduced to create an update. Visual Delta consumes only the Deno-free specification tool in development and retains its existing audit and compare-only browser gates. The operator requests a final merge pass and gives standing approval for per-repository activation after passing source acceptance; advisory exceptions and global full rollout are not implied.

The operator-approved next activation adds only Spec Validator after its source7 mergedf3bab11837648045540bf7ef948503131dcab041 and main Check44174151693 passed. Read-only existing-App probe44173967888 passed. Its normal functional no-Lapis-input contract preserves the current zero-update graph; no Changesets writer, dependency bump, version/tag or publication is invented. Notebook remains the sole exercised dependency-writing consumer; all other entries and existing holds/exclusions remain unchanged, and global phase stays pilot. Actual completion, ordinary no-update settlement and repeat receipts are recorded in the source activation record; source registration alone is not claimed as a new publisher or multi-consumer update proof.

Visual Delta adoption79 and activation77 are deployed after current source acceptance. Ordinary runs44182784733 and44182833366 qualify e755e2a0 with no updates, holds or waits, retain the same unchanged operation and form the verified durable state chain178→179. Exact source, Pages, artifact and state receipts are in the activation record. Notebook, Spec Validator, Visual Delta, Terminal and Registry are the pilot entries; other entries, exclusions, global phase and holds remain unchanged. Visual Delta’s independent guard admits only compatible Node-only validator0.2 development patches. No new dependency update or publisher execution is claimed.

VD-GOV-008 continues to gate audit remediation and package publication. The earlier blanket maintenance hold was too broad; the existing unapproved HIGH remains a publication blocker. This adoption does not change audit collectors, waive a finding, rebind an exception or authorize tags, uploads or baselines.

Parallel source registration covers six additional existing workflow sets but changes no rollout phase or writer admission. Agent Redaction remains explicitly held and ignored as a Deno package in every phase; all other acceptance, source guard, publication, ownership and state-concurrency requirements remain binding.

Requirement. Opted-in source preparation MUST constrain normal wave admission even after publication waits clear. Unsupported update sets or missing source-policy evidence MUST remain held before consumer writer admission.

Acceptance details

  • The existing bounded profile MUST require its complete source-bound single-development patch facts, not merely a matching package name or a successful upstream release.
  • Mixed or unsupported updates and inconsistent source evidence MUST stay visible, while a mixed node MAY admit only its complete schema2 policy subset; selected edges remain blocked by waits for their own dependency or unscoped waits, but MUST NOT inherit a different package’s same-manifest wait, which remains visible and blocks its own update.
  • Supported source-owned patches and ordinary repositories without an opt-in MUST retain their existing admission paths and every qualification, ownership, registry, rollout and publication gate.
  • Ordinary candidate preparation MUST still validate the complete frozen install and mechanical lock/canonical closure; DA-REL-006’s tooling artifact proof MUST NOT count as full private candidate qualification, which remains required before merge/completion, and pre-admission evidence MUST NOT assert unrun qualification or authorize a product migration.

Terminal and Registry activation

The operator’s standing post-merge approval promotes only Terminal and Registry from full to pilot after their current source/main/callback acceptance. All other phases, global pilot settings, exclusions, source holds and advisory bindings are unchanged. Exact evidence belongs in the activation record.

Terminal source27 merged50d1bb9f with qualified macOS CI, spec Pages and actual false version intent. Its independent Core0.13 development-patch guard qualifies the real released0.13.4→0.13.5 candidate, including the no-note full version recipe; the coordinator’s empty-Changeset flag remains unchanged. Registry source184 merged69d8c063, passes current Checks/signed publication and actual callbacks, and retains its private API0.1/no-version contract. Its upstream API publication wait remains binding; activation does not waive that prerequisite or claim an invented npm release. Ordinary live settlement and replay are required after policy deployment.

Held source completion observation

Desktop may explicitly observe its registered successful CI/Pages completions while its private projection write hold and phase full remain intact. DA-NOT-004’s metadata observer is not dependency admission or publication qualification. Existing hold, registry, current-main, ownership and per-entry activation checks remain required; excluded roots cannot opt into this path.

Plugins and Agent UI activation

The operator’s standing post-merge approval promotes only Plugins and Agent UI from full to pilot after exact-source, current-main and verified completion acceptance. Their existing empty-Changeset settings stay unchanged: each real version recipe correctly returns false intent without a forced empty note. All other phases, holds, exclusions, global pilot settings and exact advisory bindings remain unchanged. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; unavailable upstream publication floors are not waived, and no dependency update, version PR or publication is invented to force activity.

AI and JJ Store activation eligibility

Standing post-merge operator approval promotes only AI and JJ Store from full to pilot after independently green source adoption and whole-recipe acceptance. Both entries add the proven emptyChangeset: true capability: an actual managed empty note lets the source CLI classify supported development intake without inventing version or publication intent. Their real no-note macros alone do not prove the changed-candidate guard succeeds. The bounded activation receipt retains those separate controls and exact current-main observations.

This is eligibility, not a current-main qualification override. Pending or failed current CI, source/audit policy, ownership and publication prerequisites still hold actual writes and release-chain advancement. Existing seven pilot entries, every other empty-note setting, exclusions, holds and global pilot gates remain unchanged. Ordinary live reconciliation, exact settlement and repeat acceptance remain open until their own receipts exist. The user’s unrelated JJ Store main/release repair exclusion does not alter the collector or assert a pass.

Mira, Design Core, Tasks and Docs activation

Standing post-merge operator approval promotes only Mira, Design Core, Tasks and Docs from full to pilot after independently green source adoption, current-main checks and verified completion callbacks. Mira retains its existing emptyChangeset: true flag; the other three introduce no forced empty note. Desktop’s private-archive holdReason, every Deno/community/Nostr exclusion, every other phase/flag and global pilot settings remain unchanged. Active advisory approvals stay empty after the picomatch retirement. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; retained branch-ownership holds and upstream publication waits are not waived, and no dependency update, version PR or publication is invented to force activity.

DA-WAVE-009 — Source-bound SDK scope

Requirement. A separate explicit operator grant MAY isolate only Desktop’s root SDK development patch when exact immutable source/private-shape/canonical bindings and complete current-source qualification prove independence from enumerated frozen prerequisites.

Acceptance details

  • Both exact artifact and scope grants MUST bind the descriptor, canonical policy and immutable private shape; the source MUST already be pilot with no explicit operator hold; default-empty policies grant no phase change, audit decision or publication authority.
  • Frozen prerequisite separation MUST use structured exact path/field/name registry findings for runtime AI/Profile and development Tasks; unknown, local-path, coverage, source-CI, identity, audit and selected-SDK constraints MUST remain blocking; matching human text cannot grant authority.
  • Reports MUST retain deferred updates, typed holds and waits while only the selected SDK reaches ordinary canonical preparation and native frozen generation; private source/candidate audit and functional gates remain mandatory; all other dependency writers stay held.
  • Exact scope authority MUST enter operation identity and be rechecked during configuration, generation and copyback; candidate ownership, source/registry integrity, compatibility, fresh target revalidation and durable CAS remain mandatory; unknown or revoked grants MUST fail closed.

Tagged publisher verification recovery

Agent UI DA-PUB-005 verification-only same-run recovery authenticates the original publication independently from the immediately following successful verification. It changes no writer/state gate, channel, release floor, current-source coverage or consumer admission. The actual0.2.9/0.2.7 pair and remaining independent holds are recorded in spec/records/2026-11-18-agent-ui-verification-recovery.md.

Release intent

DA-WAVE-009 may select only a separately authorized Desktop root SDK development patch before DA-REL-006 artifact generation. Its exact grant is checked during configuration and again before generation and artifact copyback. Missing, changed or revoked scope authority grants no candidate writes. Full private-archive source/candidate functional and audit gates remain separate and mandatory.

scripts/prepare-pr.mjs runs only from Renovate’s branch-scoped context. It proves the candidate can install without rewriting the lockfile or running package hooks, compares affected active manifests and delegates deterministic Changeset writing to src/changesets.mjs.

Schema2 candidate eligibility uses the existing exact reviewed channel view for each selected manifest edge before preparation. All targets in the batch still require source policy/facts, patch compatibility and exact integrity; missing scope, moved tags or invalid publication proof retain the whole hold. When a node also contains unrelated updates, the complete policy-mapped subset may proceed only after those unchanged checks pass, and every unselected update retains its own visible hold rather than inheriting preparation authority. The ordinary available pool and schema1 independent-development profile remain unchanged. A schema2 edge still cannot bypass a wait for its selected dependency; an unrelated package’s same-manifest wait remains visible but cannot suppress a complete selected edge solely through path coincidence.

DA-REL-001 — Candidate install before release intent

Requirement. The post-upgrade helper MUST prove the exact candidate frozen install before writing dependency release intent.

Acceptance details

  • Missing or invalid Renovate branch context MUST fail.
  • The install MUST use --frozen-lockfile, --ignore-scripts and --ignore-pnpmfile.
  • Workspace catalog changes MUST inspect every active affected consumer, including peer contracts.
  • DA-REL-006 MAY prepare SDK artifacts only after its frozen projection verification; it MUST NOT create runtime release intent or substitute tooling evidence for full private-archive candidate qualification.

DA-REL-002 — Appropriate release targets

Requirement. Runtime, optional-runtime and peer first-party manifest changes MUST create release intent only for permitted versioned packages.

Acceptance details

  • Development-only changes MUST NOT trigger package release intent, and private packages MUST remain excluded unless the owning Changesets config explicitly versions them.
  • Required empty Changesets MAY preserve a repository’s release-intent convention without publishing a private application.
  • For an explicitly configured private root, an actual first-party runtime, optional-runtime or peer change MUST select the empty note while package release intent remains null, even when the source Changesets config normally versions private packages; retries MUST remove incompatible generated bump metadata from that deterministic bot note while preserving its body.
  • Missing Changesets configuration or base branch MUST fail before release-intent writes.

DA-REL-003 — Deterministic Changesets

Requirement. Repeated updates on the same automation branch MUST update one deterministic Changeset while preserving valid existing intent.

Acceptance details

  • The Changeset path MUST derive from branch scope; package names MUST be unique and sorted.
  • Existing valid bump types and authored body MUST be retained; newly affected packages MAY add patch intent.
  • Invalid existing frontmatter or bump types MUST fail rather than overwrite uncertain intent.

Publication boundary

Changesets prepare versions. They do not authorize npm publication, signed archives, GitHub release assets or registry submission.

DA-TOOL-003 adds a manifest/lock comparison after the existing scripts-disabled frozen install and before Changeset writes. New unqualified CLI adoption or incompatible cohort changes fail; unchanged legacy tooling is reported without forcing a consumer migration. Advisory policy and publication remain source-owned.

DA-REL-004 — Source-owned canonical intake

A repeated schema1 preparation MAY inspect one changed maintenance Changeset only at the exact branch-derived path. It MUST be a regular valid UTF-8 file of at most 8192 bytes with blank or empty-map release metadata; null, arrays, nonempty/malformed headers, preambles, wrong paths/scopes, multiple notes or missing/unsafe files MUST fail before any canonical write.

The filesystem boundary canonicalizes the trusted caller-owned workspace root once, preserving strict exact-path checks for every descendant input and output parent even when the host exposes that root through a platform path alias.

Canonical preparation MUST NOT generate, overwrite or claim ownership of that note. Existing authored body and product intent remain intact; nonempty schema2 runtime intent retains its separate release-target validation.

Requirement. Opted-in dependency preparation MUST carry accurate source-owned canonical facts into the same candidate without exempting main specification checks.

Acceptance details

  • The immutable admitted source MUST authorize a bounded declarative policy, exact canonical paths and unambiguous managed slots; missing or changed policy and manual content MUST remain held.
  • The initial profile MUST permit only one compatible development package, its matching existing override and mechanical registry lock closure while retaining public contracts and existing release intent, with exact selected-version boundaries preserving unrelated prefix-sharing identities.
  • Preparation MUST preserve authored content and the immutable workspace newline ending while emitting deterministic current facts without executing candidate code or asserting unrun qualification.
  • Exact chapter and governed workspace output paths MUST survive native Renovate artifact collection and final commit selection, while stale sources, unexpected changes and unsupported lock deltas MUST fail before writes.

DA-REL-005 — Workspace canonical preparation

The schema2 workspace profile records actual declared/resolved ranges, locked versions and integrity fingerprints in each source-owned slot. Its compact table is current dependency evidence, not a release or functional acceptance claim. Source-owned paths and policy bytes remain immutable throughout native generation; the existing schema1 development/override profile retains its stricter mechanical lock comparison and independent-admission boundary. Managed workspace slots retain ordinary Markdown formatter output byte for byte, so formatting never makes a valid source opt-in stale on the next update. The immutable slot may use exactly the generated one-line digest paragraph or one newline immediately before its 64-character lowercase digest. Preparation MUST preserve that source-selected form in each candidate and repeat; arbitrary whitespace, paragraph, table, hash or marker changes remain held.

Existing source-owned authored chapters may already exceed the renderer’s ordinary400-line or32KiB bounds. Schema2 may preserve those exact immutable chapters only when neither line nor byte count increases; ordinary chapters retain both fixed bounds. This adds no configurable higher budget and changes no schema1 behavior, source mapping, authored text or managed-slot authority. A later larger fact rendering remains held for owning-source review.

Requirement. Source-owned workspace preparation MUST emit current dependency facts only for explicitly admitted compatible registry updates across its declared importer and chapter scope.

Acceptance details

  • Immutable policy bytes and complete active importer coverage MUST bind chapter slots, declared ranges, registry versions and expected integrity before writes.
  • Other manifest fields, direct importer identities, workspace settings, first-party metadata and first-party edges MUST retain their independently governed source contracts.
  • Explicit third-party registry closure regeneration MAY follow the scripts-disabled frozen install while retaining tooling, audit and functional gates.
  • Manual or stale facts, external resolution, same-version integrity drift and unexpected candidate paths MUST fail without writing any chapter.

Independent development admission

Native generation MUST admit both the development manifest edge and its exact same-name workspace override; an admitted manifest alone is not a complete candidate.

DA-WAVE-007 reuses the same development fact validation for independent admission. Its single forward patch must retain public peers and exact source-owned override closure. Retaining source policy bytes in the internal public inventory binds its parsed policy to the original digest; older or changed evidence cannot activate the capability. Actual candidate preparation still verifies the exact source, unchanged policy/slots and complete mechanical lock closure before PR writes.

DA-WAVE-008 applies that source capability to normal admission too. A completed upstream publication chain cannot admit an update set outside the consumer’s declared preparation profile. Unsupported sets remain explicit holds before a writer token or Renovate execution, instead of creating recurring artifact-error PRs. Repositories without an opt-in keep their existing behavior; expanding a source policy or qualifying a product/API migration remains source-owned work.

DA-REL-006 — Inactive seeded SDK artifact capability

Requirement. A private Desktop SDK artifact projection MUST require both an immutable source descriptor and a separate exact trusted coordinator capability, with no live entry enabled by this capability change.

Acceptance details

  • The bounded root-development-only profile MUST freeze all nonselected manifest/workspace/portable-lock fields and exact private source-inventory/CI-docs bytes; only selected SDK identity, importer, existing override and registry integrity may normalize, without masking generic peer hashes or another SDK context.
  • Native pinned Node24/pnpm generation MUST seed the actual existing SDK/jiti/TypeScript closure, disable scripts/hooks and credentials, verify the projection frozen and surgically copy only independently proved native SDK blocks; no-op output MUST preserve original full bytes, and unrelated/shared/metadata/closure changes MUST fail before copyback.
  • Only the explicitly selected regex manager MAY defer artifacts to the existing trusted preparation hook; its actual extraction, artifact/post-task collection and final commit behavior MUST be qualified against real pinned Renovate, while ordinary npm profiles and all canonical/candidate/native checks remain required.
  • Source data MUST NOT clear a private/rollout/CI/publication/audit hold or grant activation; a projection is not full Desktop installation or a production-clean claim, and source-owned eight-archive/audit/product gates plus a separate later eligibility decision remain mandatory.

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.

Deno-free tooling and cohort drift

Central tooling controls qualify versioning contracts and record supported source-bound cohorts. Consumer recipe adoption remains separate; evidence refresh does not upgrade consumers, remove frozen-host prerequisites or activate writes.

DA-TOOL-001 — Reviewed versioning runtime

Requirement. Newly generated version preparation MUST execute only a reviewed Node-based Changesets contract before acquiring App write authority.

Acceptance details

  • Exact CLI version, npm integrity, Node engine metadata, executable hash and qualified Changesets configuration must identify the reviewed contract.
  • Both existing Changesets majors must remain supported without implicit major migration.
  • The generated runner must reject changed executables, unreviewed configuration and Deno formatter inputs before App minting; it must not install Deno or force another formatter.
  • A fresh generated consumer must prove version and changelog mutation with Deno absent; publication remains outside the recipe.

DA-TOOL-002 — Revision-bound compatibility cohorts

Requirement. Inventory MUST report explicit repository-specific Node, pnpm and browser-test tool cohorts using the inspected source revision and lockfile.

Acceptance details

  • Missing lock evidence and unconfigured repositories must remain coverage gaps, never qualification.
  • Playwright/test and Vitest/browser pairs must remain compatible; recorded Vite and Storybook families may differ between repositories.
  • Observed cohort constraints must not be described as complete consumer qualification or used to manufacture dependency edges.
  • Cohort policy must not contain advisory exceptions or waive functional, visual, accessibility or audit gates.

DA-TOOL-003 — Candidate drift guard

Requirement. Production candidate preparation MUST reject newly introduced unqualified versioning runtimes and incompatible tool-cohort changes before writing release intent.

Acceptance details

  • The guard must compare the candidate with its exact previous manifest and lock evidence after the frozen install with scripts disabled.
  • Unchanged legacy tooling may remain visible without forcing a migration; changed CLI bytes, unreviewed versions and implicit major switches must fail closed.
  • Existing excluded hosts, source-owned advisory bindings, expiries and security update ownership must remain unchanged.
  • Rollout and write authority must remain governed by existing operator gates.

DA-TOOL-004 — Cohort evidence and recipe separation

Requirement. Expanded cohort records MUST retain exact manifest/lock and successful source-CI context separately from whole-recipe runtime qualification.

Acceptance details

  • Records MUST bind exact source, manifest/lock SHA256, resolved tool versions and the latest observed successful default-branch source-pipeline run, with prior-source or unavailable evidence explicit.
  • A successful source-CI run MUST NOT qualify a version recipe as Deno-free, and an absent manifest command MUST NOT imply an absent workflow recipe.
  • Inventory MUST report source/lock drift and missing evidence without turning historical source success into current qualification.
  • Collection MUST remain GET-only within eligible public allowlist entries, preserving holds, excluded hosts, frozen tasks and all existing consumer gates.

DA-TOOL-005 — Reviewed source workflow outcomes

Requirement. Reviewed source-CI evidence MUST select only reviewed repository-specific workflow paths and successful required jobs bound to the same source, run and attempt. Missing, skipped, duplicate, incomplete or unavailable job evidence MUST NOT qualify a run. An explicitly empty workflow policy MUST remain unavailable without filename fallback.

Acceptance details

  • Successful release or deployment metadata alone MUST NOT replace required validation outcomes.
  • Historical records without job receipts MUST remain explicitly run-only observations.
  • Prior-source success and current-source failures MUST remain distinguishable; source CI MUST NOT establish whole-recipe portability.

DA-TOOL-006 — Exact package-manager provenance and refresh

Requirement. Existing-cohort refresh MUST preserve supported tool ranges and package-manager versions. An undeclared root package manager MUST remain undeclared; a reviewed workflow pin MAY be recorded separately using exact source bytes and step coordinates. Collection MUST propose evidence only within existing eligible public scope and MUST NOT change policy, source, activation or advisory authority.

Acceptance details

  • Changed or ambiguous workflow commands, unsupported resolved versions and changed package-manager versions MUST fail closed.
  • Refresh MUST report declared-range differences separately without silently widening supported cohorts.
  • Excluded or held sources, frozen tasks and missing whole-recipe qualification MUST retain their boundaries.

DA-TOOL-007 — Reviewed development input coordinates

Requirement. A source-reviewed version recipe MAY bind one pinned first-party development override as compatible patch data. Every other workspace byte, installed versioning executable, configuration, command and runtime constraint MUST remain bound before writer admission. Existing consumers without this opt-in MUST retain exact file binding.

Acceptance details

  • The opt-in MUST name one development-only package, a stable major/minor series, a minimum patch and the workspace fingerprint with only that exact override value normalized.
  • The manifest development pin, installed package identity and unique direct workspace override MUST agree.
  • Runtime dependencies, patches below the reviewed minimum, prereleases, ambiguous/missing selectors and other workspace changes MUST fail closed; forward-only update admission remains independently required.
  • Source-owned whole-recipe proof, frozen installation, candidate functional/audit gates and no-intent handling MUST remain separate requirements.

Registry evidence and rollout limits

The planning assumption that Changesets 3 requires Deno is corrected by the integrity-verified npm 3.0.3 tarball: its executable uses Node and its engine requires “^22.11 || ^24 || >=26”. Both 2.31.1 and 3.0.3 ship no Deno references. The redundant upstream version-only template setup can therefore be removed. Notes’ separately owned frozen-host tooling remains untouched.

Changesets 3 can invoke Deno through its transitive formatter. Format 0.1.3 detects deno.json/deno.jsonc ahead of Prettier in the same directory. A Node executable does not prove arbitrary project recipes Deno-free. The generic contract conservatively holds Deno declarations in its formatter lookup ancestry and changed Changesets configuration for source-owned qualification.

Reviewed validator patch in the existing pilot

DA-TOOL-003 admits the separately reviewed Deno-free spec-validator0.2.1 patch alongside0.2.0 in the existing Plugins, Mira, Core, Notes and Notebook pilot cohorts. This exact two-version set does not admit future patches or minors, force any consumer migration or change Node/pnpm/CLI/browser constraints. Historical evidence remains attached to its original source, lock and resolved versions. It is not rewritten to claim new candidate or recipe qualification.

The post-upgrade hook still requires the frozen scripts-disabled candidate install and all original drift checks before release-intent preparation. Missing required intent or an artifact error MUST NOT establish a completed release chain, regardless of a successful coordinator workflow exit. Native Renovate artifact-error review and current-head consumer gates remain binding. No excluded hosts, phase, scope, advisory approval or permissions change.

Reviewed owner-cohort policy repair — November 17

GET-only refresh continues preserving supported constraints and reporting declaration differences for review. The reviewed policy now records the source-qualified Docs, Agent UI and Terminal Storybook10.6.7 cohorts, paired Vitest4.1.12 where changed, Docs Vite6.4.6 and Visual Delta Spec Validator0.2.1. These twelve exact constraint changes retain Node, pnpm, Changesets majors, runtime bytes, source recipes and all other owner constraints. Docs, Agent UI and Terminal also gain exact required-job receipts from their existing complete source workflows; no filename fallback replaces reviewed selectors.

Mira’s previously empty selector is explicitly replaced with its reviewed mira-spec-first.yml workflow and all three governance, package and browser jobs. This policy decision accepts actual required-job receipts; an empty selector elsewhere continues to mean unavailable, without fallback.

All sixteen observations bind their inspected public source, manifest, lock and resolved tools. All sixteen have same-source successful CI observations; reviewed job receipts and historical run-only observations stay distinct. Recipe qualification continues to be reported separately from source/cohort evidence and the ten deployed whole-recipe guards. Existing Deno-root exclusions remain explicit dependency-write holds under DA-POL-003, including during full-phase simulation.

Operational drift and advisory admission

DA-OPS-001 — Bounded operational observations

Requirement. The production maintenance audit MUST report exact-source template/runtime, update-owner, exclusion, activation and required-check observations with explicit unavailable or unknown coverage.

Acceptance details

  • Local composite actions MUST be resolved recursively at the same source revision; missing, cyclic or unsupported action/workflow bodies MUST remain explicit coverage gaps.
  • Reviewed action pins and Node versions MUST be compared without interpreting arbitrary scripts as a complete security analysis.
  • Required-check settings MUST be read separately from source PR-job candidates; inaccessible protection/rules APIs MUST NOT prove coverage or absence of requirements.
  • Activation reads MUST retain only allowlisted public-safe booleans/phase from the Variables API or the exact main audit workflow’s observed Actions context, with explicit provenance; exclusions and update ownership MUST remain visible without changing settings.

DA-OPS-002 — Exact advisory decisions

Requirement. Coordinator write admission MUST reject every audit finding except an explicitly approved, unexpired exact advisory/package/version/path/dependency-source/lock binding with no known published fix.

Acceptance details

  • The approval authority MUST default empty without inherited exceptions or automatically created approvals.
  • Malformed, incomplete, muted or unavailable audits and unknown fix metadata MUST fail closed; additional findings, mismatches, expired approvals and available fixes MUST reject writes.
  • The source binding MUST identify the immutable most recent manifest/lock commit and the SHA256 of exact lock bytes, allowing a separately reviewed policy-only approval without a self-referential commit hash.
  • Unmatched approvals MUST be reported as stale cleanup findings and MUST NOT silently authorize future findings; fixes MUST require approval retirement.

DA-OPS-003 — Pre-admission execution

Requirement. Real coordinator audit qualification MUST precede writable wave admission and App token minting while preserving read-only inventory and state-only pilot observations.

Acceptance details

  • Inventory MUST run the complete scripts-disabled coordinator audit and emit a public-safe decision; denied writes MUST produce no writable target matrix or new writable admission.
  • Reconcile MUST repeat the actual preflight before writer App minting; a prior report alone MUST NOT authorize writes.
  • Read-only collection and state-only reporting MUST remain possible with unapproved findings, without modifying activation, repository protections or credentials.

Recorded decisions

The operator approved the exact coordinator deepmerge decision proposed in PR21 on November 16. config/advisories.json owns its dependency-source/lock/path/version binding and November 21 expiry. The decision record records that scope; all rejection and cleanup requirements above still apply.

The reviewed activation checkpoint records writes=true, phase=pilot, waves=true, schedule=true and state-writes=true after the genuine Notebook candidate, main and normal replay qualify. Live variable read-back records activation at 2026-11-17T19:03:07.167Z. This comparison checkpoint does not change absent-variable/ default-off workflow semantics or external settings. The timer configuration, actual callbacks and ordinary-run receipts remain separate observations.

The operator separately approved the validator-update rebinding in PR34 to dependency source9d657a74 and exact lock SHA256a3e1f05f…ca61b8b. This replaces the stale prior tuple without extending the November21 expiry or adding any advisory, package path, scope or rollout authority. config/advisories.json remains the sole machine-readable approval authority; raw audit observations and version recipes cannot renew it.

The exact approval is subsequently retired under DA-OPS-002 after upstream withdrawal at2026-11-16T18:55:38Z and complete zero-finding audit evidence. Hosted43960484629 correctly held writes on the stale cleanup item; reviewed removal restores the empty approval list without changing any rejection rule, source/lock bytes, scope, activation or pilot gate. The retirement record retains the before/after preflight and pending hosted reconciliation distinction.

Picomatch observation and exact approval — November 17

Fresh coordinator audit reports HIGH GHSA-fc5q-39xc-vjpf on picomatch2.3.2 and 4.0.7 at two exact Renovate runtime paths. The dependency-source/lock bytes are unchanged; the earlier clean observations and retired LOW decision cannot authorize these findings. Normal audit admission denies writes before App minting, and the operator also places the consumer writer switch off while scheduling remains off. The disabled proposal in docs/proposals/picomatch-high-2026-11-19.md grants no authority; DA-OPS-002 still requires a fixed dependency graph or explicit exact operator decision.

The operator subsequently explicitly approves exactly the two proposal bindings at 2026-11-17T18:15:39.194Z, expiring exclusively November19,2026 at00:00UTC or sooner on a known published fix. Active policy retains unchanged dependency source9d657a74/locka3e1f05f and reviewed proposal PR69. Fresh preflight must accept only those two paths; raw audit still reports HIGH, all other gates remain blocking, and hosted deployment/regeneration acceptance is separate. The activation evidence records before/after qualification without treating the graph as clean.

Those exact HIGH approvals are subsequently retired under DA-OPS-002 after upstream withdrawal at2026-11-18T15:38:56Z and complete zero-finding audit evidence. Preflight correctly holds writes on two retire-stale-approval cleanup items until reviewed removal restores the empty approval list without changing any rejection rule, source/lock bytes, scope, activation or pilot gate. The retirement record retains the before/after preflight and pending hosted reconciliation distinction.

The retained exclusion checkpoint also names lapismd/agent-redaction and @lapismd/agent-redaction, matching the operator’s Deno-package exclusion. Removing either remains observable drift; this is not an advisory decision or activation change.

Release notifications

The scoped channel and static-publication readers preserve DA-NOT-001/002/003: notifications remain hints, not publication or channel authority. Independent fresh registry, signature, source and current-CI evidence owns admission; the existing completion payload, callbacks and credential boundary are unchanged.

Publishers call the pinned notify.yml reusable workflow after their verified publication boundary. The caller supplies the exact coordinator revision and original source SHA. Notification failures can be retried independently of package publication.

DA-NOT-001 — Verified source notification

Requirement. Publication notifications MUST validate an allowlisted source revision and discover its stable public first-party packages before dispatch.

Acceptance details

  • Source revisions MUST be 40-character commit SHAs and package versions MUST be stable semver.
  • Private, unversioned and non-first-party packages MUST be excluded.
  • Each notified coordinate MUST exist in npm metadata with matching name/version and integrity.
  • No matching published packages MUST produce no dispatch; other registry failures MUST fail.

DA-NOT-002 — Hint and recovery semantics

Requirement. lapis-npm-published-v1 dispatches MUST be hints for registry reconciliation rather than trusted version or publication authority.

Acceptance details

  • The coordinator MUST validate the source, SHA and package payload before inventory.
  • The receiver MUST rediscover current registry eligibility instead of applying payload versions directly.
  • Missing notification setup MUST leave manual reconciliation and explicitly gated hourly catch-up as recovery paths.
  • A failed dispatch MUST identify retrying the notification rather than replaying publication.

Credentials and checkout wiring

The notifier uses a coordinator-scoped App token for repository_dispatch and the caller’s read token for source discovery. Its pinned checkout runs the requested coordinator commit. The notification key remains encrypted in the existing workflow secret boundary; this repository stores no key values.

The dedicated reusable completion.yml accepts only trusted default-branch workflow_run callers. Its lapis-dependency-completed-v1 hint contains public repository/source coordinates and the notifying callback run/attempt identity; it never qualifies CI by itself. Publication hints use exact public source discovery; completion hints use public workflow and current-head metadata only, without fetching candidate trees/files or npm metadata. Publication coordinates are checked again against registry integrity. Full scans coalesce by immutable registry identities regardless of arrival order.

Receivers retain only the documented source/version coordinates, discarding unknown payload fields before writing public artifacts.

DA-NOT-003 — Verified completion wake-up

Known, non-held consumers may continue supplying verified completion observations while outside the writable pilot. Callback scope does not grant write admission; the current phase, candidate and ownership gates still select every writer. Notebook’s source policy admits only its exact active CI, Pages and version workflow IDs/paths. Registry release and callback self-triggers are not admitted; the source-owned npm publication notification remains a separate boundary.

Docs and Tasks register only their existing CI/npm and Storybook Pages workflow IDs/paths/events for the next adoption wave. Versioning is a job inside their CI workflow, so no separate version workflow is invented. Registry distribution and callback self-triggers remain excluded. Both entries stay full; these read-only completion identities grant no consumer write or audit authority.

The next small-repository slice registers Spec Validator’s existing Check workflow and Visual Delta’s existing CI, PR-specification, Pages and version workflows by exact IDs, paths and supported events. The read-only App probe adds only those two exact targets. Tag publishers, native capture, image publishers and callback self-triggers are not completion sources; verified npm notifications remain separate. Both repositories retain phase full until their merged source acceptance and a separate per-entry activation/replay. Spec Validator currently consumes no Lapis npm dependency; no synthetic Core pin or version recipe is introduced to create an update. Visual Delta consumes only the Deno-free specification tool in development and retains its existing audit and compare-only browser gates. The operator requests a final merge pass and gives standing approval for per-repository activation after passing source acceptance; advisory exceptions and global full rollout are not implied.

Requirement. Completion callbacks MUST verify successful current non-fork source workflow evidence before minting a coordinator-scoped dispatch token.

Acceptance details

  • Trusted pinned coordinator code MUST compare the actual run ID, attempt, SHA, event and exact allowed workflow ID/path with read-only GitHub evidence; unknown, failed, stale or inaccessible coverage MUST withhold dispatch.
  • The source MUST be explicitly public, and its head MUST match an open same-repository PR or the current default branch; revalidation immediately before dispatch MUST reject a moved head.
  • Default-branch workflow_run callers MUST read or execute no candidate files, code, artifacts or caches, retain the existing notification credential boundary, and exclude their own workflow from completion triggers.
  • Completion hints MUST leave all-current-head CI, repair ownership, registry discovery and merge/publication authority unchanged.

Parallel source registration

Exact existing source workflows for Server, Agent UI, AI, Terminal, jj-store and Plugin Registry are registered for their supported PR/push/manual events. Unsupported workflow_call/merge_group events, callback self-triggers and nested image/cache/native/tag/publisher entrypoints are not added. Registry’s top-level signed deployment is its actual completion boundary, not an invented npm release. Registration is read/dispatch authority only; each source caller must pin this reviewed implementation and policy together and pass independent source/main acceptance before a separate per-entry activation and durable replay.

Desktop’s existing CI400533153 and Pages403244157 are the only new registered workflows. CI supports original PR/push/manual events; Pages supports push/manual. Scheduled CI, preview/trial/image/health publishers and callback self-triggers remain excluded. Desktop’s private projection hold and phase full remain unchanged; source acceptance and a separate reviewed activation still apply.

DA-NOT-004 — Held source observation

Requirement. Held metadata observers MUST preserve every dependency-write, publication and activation hold.

Acceptance details

  • heldObservers MUST explicitly name a registered full-phase repository with an existing nonempty write hold; missing, duplicate, unknown or prematurely promoted opt-ins MUST fail closed.
  • Monitoring-excluded roots MUST remain ineligible even when an observer opt-in is supplied.
  • Observation MUST retain the same exact source/run/workflow/head checks and metadata-only callback boundary without clearing holds, modifying source or granting publisher authority.

Monitoring and App readiness

Monitoring is read-only collection, distinct from dependency-update admission. The current audit identifies direct known PR creators in default-branch workflow YAML. It is not a complete call-graph or workflow-security analysis.

DA-MON-001 — Auditable workflow reads

Requirement. Maintenance audit MUST inspect exact default-branch workflow revisions using read authority and retain explicit coverage outcomes.

Acceptance details

  • Reports MUST include schema version, collection time, repository source SHA and workflow paths.
  • Read, parse or truncated-tree failures MUST produce an unavailable coverage entry and a failing exit status.
  • Partial reports MUST still be written and retained by the hosted workflow.
  • Unexpected errors, API bodies, tokens and unallowlisted environment values MUST NOT enter reports.

DA-MON-002 — Bounded authentication findings

Requirement. Authentication findings MUST distinguish workflow-token writers, recognized App-token references and unverified references without claiming more coverage than the detector provides.

Acceptance details

  • Direct gh pr create/edit, Changesets and known PR-creation actions MUST be inspected.
  • Environment token resolution MUST respect workflow, job and step precedence.
  • An arbitrary token output MUST NOT prove App authentication.
  • Findings MUST remain recommendations; inaccessible coverage MUST remain distinct from a clean audit.

DA-MON-003 — Read-only readiness probe

Requirement. The manual main-only App probe MUST verify exactly one explicit pilot repository with read-only contents/PR authority.

Acceptance details

  • Pilot choices MUST resolve through the exact reviewed repository-to-owner mapping before App minting.
  • The token’s installation scope MUST contain exactly that repository.
  • Repository and PR reads MUST succeed without changing branches, PRs, reviews, settings or secrets.
  • Successful reads MUST NOT be reported as proof of write readiness.

Coverage limits

The audit does not inspect script internals or remote reusable workflow bodies. DA-OPS-001 adds recursive local composite resolution, reviewed pin/Node source comparisons, update ownership, exclusions and activation observations. Required check settings are compared conservatively with static PR job candidates; missing APIs, filters, matrices and dynamic names retain unknown coverage. Matching names do not prove functional coverage or green current-head checks. No persistent issue collector or unattended operator UI is implemented here. Maintenance’s separate browser adapter consumes monitoring defaults while retaining its own credential and command boundaries.

Changesets creators may reference with.github-token as well as the legacy GITHUB_TOKEN environment variable. The detector retains the legacy explicit environment precedence and recognizes the source’s pinned v2 input-only App reference; unknown outputs remain unverified. It reports references, not actual token values or proof that a particular action version can execute successfully.

The audit may observe its five allowlisted activation settings from GitHub’s resolved vars context when the Variables API is unavailable. This fallback requires the exact coordinator repository, main ref, audit workflow ref, supported event and source SHA; local or incomplete contexts remain unavailable. Reports retain sanitized values and their provenance under DA-OPS-001.

The next Docs/Tasks source preparations may invoke the same reviewed App readiness workflow for their two explicitly named repositories. Tokens remain restricted to one selected repository with contents/PR reads only; no source checkout, credential retrieval/rotation or writer activation is added.

The next small-repository slice registers Spec Validator’s existing Check workflow and Visual Delta’s existing CI, PR-specification, Pages and version workflows by exact IDs, paths and supported events. The read-only App probe adds only those two exact targets. Tag publishers, native capture, image publishers and callback self-triggers are not completion sources; verified npm notifications remain separate. Both repositories retain phase full until their merged source acceptance and a separate per-entry activation/replay. Spec Validator currently consumes no Lapis npm dependency; no synthetic Core pin or version recipe is introduced to create an update. Visual Delta consumes only the Deno-free specification tool in development and retains its existing audit and compare-only browser gates. The operator requests a final merge pass and gives standing approval for per-repository activation after passing source acceptance; advisory exceptions and global full rollout are not implied.

The parallel adoption probe adds the remaining eligible exact targets, including Mira, Core, Notebook, Desktop, Agent UI, Terminal, Plugin Registry and jj-store. Only the fixed jj-store mapping selects the personal owner. It retains no checkout, writer, secret retrieval or installation-setting mutation. A missing App installation remains a concrete read-readiness failure, not permission to copy credentials or activate that repository.

Organization profile refresh

This is the coordinator’s qualified generated-PR writer. The source-owned .github script generates npm-status Markdown without App credentials. A separate coordinator job accepts only the generated README artifact from that same workflow run and publishes a narrowly checked rolling PR.

DA-PR-001 — Isolated generation and publication

Requirement. Profile generation MUST execute without App secrets, and publication MUST run only trusted coordinator code against the same run’s candidate artifact.

Acceptance details

  • Both jobs MUST run only from main; scheduled generation MUST require its explicit rollout variable.
  • Checkout credentials MUST NOT persist.
  • Only the publication job MAY mint an App token, scoped to .github contents and PR writes.
  • Publication MUST NOT execute generator code or artifact-provided scripts.

DA-PR-002 — Exact allowed diff

Requirement. Profile publication MUST accept only configured npm-status cell changes for the exact current source revision.

Acceptance details

  • Non-table text, repository/build cells, package order/count and unconfigured cells MUST remain unchanged except permitted table padding.
  • Status cells MUST match the generated package/version grammar; size, line count and duplicate/missing rows MUST be checked.
  • Source changes before validation or final publication MUST stop the write and require regeneration.

DA-PR-003 — Rolling branch and repair safety

Requirement. The profile writer MUST preserve branch history and manual repairs while deduplicating already pending candidates.

Acceptance details

  • Open rolling reviews MUST belong to the expected repository and known bot; unexpected files or manual commits MUST stop automation.
  • Updates MUST use fast-forward-only ref writes and retain the previous branch head as a parent.
  • An identical App-owned candidate already based on current main MUST perform no writes.
  • A retained branch without an open PR MUST match an exactly merged bot review before reuse.

DA-PR-004 — Handover and uncertain writes

Requirement. Legacy profile PR creator handover MUST occur only after validated branch publication, and uncertain writes MUST require reconciliation instead of blind retries.

Acceptance details

  • The one-time legacy bot PR MAY close only after validation and branch update, then be replaced by an App-created PR.
  • Ordinary candidate CI and repository merge policy MUST remain required.
  • An orphaned branch after an uncertain PR write MUST stop automatic overwrite.
  • API failures MUST avoid response-body or credential logging.

DA-PR-005 — Profile review context

Requirement. A legitimate changed profile candidate MUST describe its bounded public npm-cell changes, exact source/candidate revisions, validation boundary and real review/recovery links in a managed PR-body section.

Acceptance details

  • Context MUST distinguish completed source/diff validation from ordinary candidate CI and maintainer review; it MUST NOT imply publication authority or completed candidate checks.
  • Rolling updates MUST preserve maintainer text outside the managed section and reject ambiguous markers before writes; the exact legacy generated description MAY be upgraded.
  • An identical pending or unchanged candidate MUST retain its GET-only no-op behavior, including when its description predates the managed section.
  • Only existing manual workflow/review links MAY be offered; no refresh checkbox MAY appear without an implemented backend.

Scheduling and merge boundary

The scheduler is hourly with manual recovery. It does not automatically merge the profile PR, approve reviews or change branch protection.

DA-WAVE-009 changes only dependency-PR context. Organization profile generation, its managed message, native diff preservation, confirmation and source-bound writer contract remain unchanged; scoped dependency authority cannot trigger a profile refresh or authorize another publication.

Workflow and module wiring

The accepted initial single-repository rollout uses Notebook in the existing pilot phase; the next qualified source entry is the no-input Spec Validator. config/completions.json also binds its actual CI, Pages and version workflow IDs; verified observer callbacks from other known non-held consumers remain accepted without enabling those consumers’ writers. The coordinator’s hourly schedule is enabled after the Notebook acceptance and normal replay receipts. The source policy retains global phase pilot, Notebook and only the separately accepted Spec Validator, Visual Delta, Terminal and Registry entries; the single-pilot record separates actual candidate/main/callback evidence, timer configuration and the first unobserved cron event. Sixteen adoption tasks reuse this same flow; no consumer copies the engine or independently enables another schedule.

reconcile.yml passes optional manual recover-source-revision only to the inventory recovery boundary. qualifyRecoverySource reads both exact public trees before recoverEmptyOperation can record a source transition. The existing exact-state CAS/read-back and consumer revalidation remain required; ordinary events cannot invoke this recovery path. reconcile-operation is a separate manual-only inventory boundary: it binds an exact completed admission and state revision, records only a strict target subset already qualified on advanced main, and returns the remaining subset to fresh ordinary planning. It does not use or widen source-recovery projection rules.

This map describes executable entrypoints. It deliberately contains no secret values, live operational reports or copied repository inventories.

DA-WIRE-001 — Explicit workflow graph

Requirement. Each hosted workflow MUST retain an explicit entrypoint, data boundary and authority consistent with its owning canonical chapter.

Acceptance details

  • Inventory and audit jobs MUST remain readers; per-target reconciliation, profile publication and the separately gated coordinator state job MUST be the explicit writer boundaries.
  • Publication notifications MUST call the registry-verifying notifier after a source-owned verified publication boundary; completion callbacks MUST use the separately verified read-only workflow-run boundary before App minting.
  • Documentation delivery MUST upload only the generated specification book.

Hosted entrypoints

WorkflowTrigger and jobsInputs and entrypointsOutputs and authority
check.ymlPR/main checksFrozen install, pnpm verifySource/spec qualification; contents read
reconcile.ymlPublication/completion dispatch, hourly catch-up, manualinventory → matrix reconcile; exact manual recovery/operation reconciliation → fresh planning; inventory/config scripts → Renovate → prepare-pr.mjsIgnored report artifacts; dry-run or explicit one-repository App writes
completion.ymlReusable trusted source workflow_run callExact allowed source run/attempt → read-only verification → existing scoped AppCompletion hint; receiver waits for callback completion; no source writes
notify.ymlReusable publisher callExact coordinator/source revisions → scripts/notify.mjsRegistry-verified dispatch to coordinator; no npm publisher
maintenance-audit.ymlDaily/manualShared monitoring policy → scripts/audit-maintenance.mjsRead-only partial/complete JSON report, 14-day artifact
app-readiness.ymlManual main-onlyOne of the explicitly reviewed repositories and existing encrypted App credentialsScope/repository/PR read proof; no target writes
profile-refresh.ymlGated hourly/manualSource generator → same-run artifact → coordinator publish-profile.mjsGuarded rolling profile PR using scoped App writes
pages.ymlMain push/manual mainFrozen install and complete verification → generated spec/bookBook-only Pages artifact; isolated Pages deployment authority

Source flow

policy + GitHub default-branch manifests + npm metadata
  -> inventory (owners, consumers, availability, cycles, holds)
  -> eligible per-repository matrix
  -> generated Renovate rules + target-scoped token
  -> exact candidate install + deterministic release intent
  -> consumer CI and existing merge rules
  -> source-owned versioning / approval / publication
  -> verified notification hint or scheduled catch-up
BoundaryOwning implementation
Discovery / registry closuresrc/github.mjs, src/policy.mjs, scripts/inventory.mjs
Central Renovate rulessrc/renovate.mjs, scripts/configure-renovate.mjs, renovate.config.cjs
Release intentsrc/changesets.mjs, scripts/prepare-pr.mjs
Consumer integrationscripts/prepare-consumer.mjs, scripts/onboard-changesets.mjs, src/consumer-ci.mjs, src/docker-context.mjs, templates/
Publication notificationscripts/notify.mjs, notify.yml
Monitoring policy / auditsrc/maintenance-policy.mjs, scripts/audit-maintenance.mjs
Profile validation / writessrc/profile-writer.mjs, scripts/publish-profile.mjs
Repository/spec checksscripts/check.mjs, spec-validator.config.mjs, package scripts

Workspace canonical preparation uses canonical-workspace-policy.mjs for source-owned schema/scope, canonical-workspace.mjs for actual facts and lock validation, and the existing canonical-intake-files.mjs adapter for immutable source/filesystem checks. canonical-admission.mjs restricts ordinary wave admission; renovate.mjs binds target integrity and exact output filters before prepare-pr.mjs invokes the shared preparer. Consumer deployment remains under DA-REL-005 qualification.

Wave wiring

src/audit-preflight.mjs runs the complete coordinator audit before inventory can plan writable admissions. scripts/audit-preflight.mjs repeats the real check before the App-token step. Read-only matrix execution no longer mints a write-capable App token. The operational maintenance audit resolves local composites from exact-source tree blobs and reads required-check/activation metadata without changing settings.

maintenance-audit.yml passes only the five allowlisted activation variables from GitHub’s vars context. When the Variables API is unavailable, the collector requires that exact main workflow/repository/ref/event/revision context and labels the observation source. It retains contents-read authority and adds no App token, settings permission or write API.

inventory reads state and current evidence, then emits the admitted matrix and candidate state. wave-state publishes that state only from trusted main with its separate gate; matrix reconcile requires that publication in writable wave mode. validate-wave-target.mjs refreshes target revision and branch ownership before Renovate. src/waves.mjs, src/wave-evidence.mjs and src/wave-state.mjs own planning, observation and state CAS respectively. The default-off wave gate leaves the original flat matrix available for rollback.

Completion adoption uses config/completions.json, src/completion.mjs and scripts/qualify-completion.mjs. The generic publisher notifier rejects completion calls before App minting. completion.yml checks out only an exact trusted coordinator revision with credentials disabled, installs frozen production dependencies without lifecycle scripts, and reads source API metadata. It revalidates after minting and dispatches no candidate data beyond documented public coordinates. The callback run/attempt in the hint is settled before inventory; all existing qualification checks remain observed.

The read-only inventory and source/book verification jobs install the owned Lapis CI setup-gh action at the reviewed immutable publication-policy pin. Publication collection verifies its exact binary/runtime/trust bytes before offline provenance checks; it grants no artifact execution or publication authority.

Trusted-main wave inventory uses its existing contents-read workflow token for public artifact downloads, with no App key, reader mint or permission probe. Discovery and publication collection remain public-only; missing read access keeps the publication unknown. Per-target writers retain their separate App credentials, actual audit preflight and admission gates.

Docs and Tasks register their actual CI/Pages completion identities while remaining outside the writable pilot. The App readiness workflow adds only these exact read-only probe targets; source callback adoption and required consumer audit qualification remain separate gates.

The next small-repository slice registers Spec Validator’s existing Check workflow and Visual Delta’s existing CI, PR-specification, Pages and version workflows by exact IDs, paths and supported events. The read-only App probe adds only those two exact targets. Tag publishers, native capture, image publishers and callback self-triggers are not completion sources; verified npm notifications remain separate. Registration74 initially retained phase full for both repositories pending merged source acceptance and separate activation/replay, now recorded below. Spec Validator currently consumes no Lapis npm dependency; no synthetic Core pin or version recipe is introduced to create an update. Visual Delta consumes only the Deno-free specification tool in development and retains its existing audit and compare-only browser gates. The operator requests a final merge pass and gives standing approval for per-repository activation after passing source acceptance; advisory exceptions and global full rollout are not implied.

The operator-approved next activation adds only Spec Validator after its source7 mergedf3bab11837648045540bf7ef948503131dcab041 and main Check44174151693 passed. Read-only existing-App probe44173967888 passed. Its normal functional no-Lapis-input contract preserves the current zero-update graph; no Changesets writer, dependency bump, version/tag or publication is invented. Notebook remains the sole exercised dependency-writing consumer; all other entries and existing holds/exclusions remain unchanged, and global phase stays pilot. Actual completion, ordinary no-update settlement and repeat receipts are recorded in the source activation record; source registration alone is not claimed as a new publisher or multi-consumer update proof.

Visual Delta adoption79 and activation77 are deployed after current source acceptance. Ordinary runs44182784733 and44182833366 qualify e755e2a0 with no updates, holds or waits, retain the same unchanged operation and form the verified durable state chain178→179. Exact source, Pages, artifact and state receipts are in the activation record. Notebook, Spec Validator, Visual Delta, Terminal and Registry are the pilot entries; other entries, exclusions, global phase and holds remain unchanged. Visual Delta’s independent guard admits only compatible Node-only validator0.2 development patches. No new dependency update or publisher execution is claimed.

VD-GOV-008 continues to gate audit remediation and package publication. The earlier blanket maintenance hold was too broad; the existing unapproved HIGH remains a publication blocker. This adoption does not change audit collectors, waive a finding, rebind an exception or authorize tags, uploads or baselines.

Parallel source preparation shares one coordinator. Exact observer registration for Server/Agent UI/AI/Terminal/jj-store/Registry and owner-mapped read probes add no writer. Source tasks may progress independently; central activation and durable reconciliation stay serialized, with unchanged global pilot settings.

Terminal and Registry activation

The operator’s standing post-merge approval promotes only Terminal and Registry from full to pilot after their current source/main/callback acceptance. All other phases, global pilot settings, exclusions, source holds and advisory bindings are unchanged. Exact evidence belongs in the activation record.

Terminal source27 merged50d1bb9f with qualified macOS CI, spec Pages and actual false version intent. Its independent Core0.13 development-patch guard qualifies the real released0.13.4→0.13.5 candidate, including the no-note full version recipe; the coordinator’s empty-Changeset flag remains unchanged. Registry source184 merged69d8c063, passes current Checks/signed publication and actual callbacks, and retains its private API0.1/no-version contract. Its upstream API publication wait remains binding; activation does not waive that prerequisite or claim an invented npm release. Ordinary live settlement and replay are required after policy deployment.

Plugins and Agent UI activation

The operator’s standing post-merge approval promotes only Plugins and Agent UI from full to pilot after exact-source, current-main and verified completion acceptance. Their existing empty-Changeset settings stay unchanged: each real version recipe correctly returns false intent without a forced empty note. All other phases, holds, exclusions, global pilot settings and exact advisory bindings remain unchanged. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; unavailable upstream publication floors are not waived, and no dependency update, version PR or publication is invented to force activity.

AI and JJ Store activation eligibility

Standing post-merge operator approval promotes only AI and JJ Store from full to pilot after independently green source adoption and whole-recipe acceptance. Both entries add the proven emptyChangeset: true capability: an actual managed empty note lets the source CLI classify supported development intake without inventing version or publication intent. Their real no-note macros alone do not prove the changed-candidate guard succeeds. The bounded activation receipt retains those separate controls and exact current-main observations.

This is eligibility, not a current-main qualification override. Pending or failed current CI, source/audit policy, ownership and publication prerequisites still hold actual writes and release-chain advancement. Existing seven pilot entries, every other empty-note setting, exclusions, holds and global pilot gates remain unchanged. Ordinary live reconciliation, exact settlement and repeat acceptance remain open until their own receipts exist. The user’s unrelated JJ Store main/release repair exclusion does not alter the collector or assert a pass.

Notes activation eligibility

Standing post-merge operator approval promotes only Notes from full to pilot after source155 merged with all required checks passing. Its existing measured emptyChangeset: true flag remains unchanged. Source policy limits supported inputs and preserves frozen hosts; publisher/channel/audit authority stays with the source. The activation record separates source acceptance, current-source release preparation and the live publication attempt. Pending current CI and upstream/publication waits continue to hold writers. Existing nine pilot entries, all other flags/holds/exclusions, empty artifact capabilities and global pilot/schedule settings are unchanged. Actual publication proof, ordinary live settlement and repeat remain required; policy eligibility alone does not complete adoption53.

Mira, Design Core, Tasks and Docs activation

Standing post-merge operator approval promotes only Mira, Design Core, Tasks and Docs from full to pilot after independently green source adoption, current-main checks and verified completion callbacks. Mira retains its existing emptyChangeset: true flag; the other three introduce no forced empty note. Desktop’s private-archive holdReason, every Deno/community/Nostr exclusion, every other phase/flag and global pilot settings remain unchanged. Active advisory approvals stay empty after the picomatch retirement. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; retained branch-ownership holds and upstream publication waits are not waived, and no dependency update, version PR or publication is invented to force activity.

Specification governance

Seeded SDK artifact data, policy, native generation and filesystem adapters map to DA-REL-006 under Release intent and Consumer integration; normal ownership, explicit capability decisions and independent source gates remain required.

The source-owned tagged-workspace publication verifier maps to DA-PUB-005 and Waves; this registration changes no publisher execution or completion authority.

S6 operational drift and advisory admission are mapped to DA-OPS-001 through DA-OPS-003. Normal source checks validate both policy schemas, retained runtime exclusions and upstream version-template pins; live audit success is a separate write preflight, never inferred from syntax/spec qualification.

The authority order is workspace/repository guidance, canonical requirements, source/public contracts and tests, then operational README and rollout records. QMD search is discovery; the returned canonical file remains authoritative.

The repository description, About website and README specification badge link to the published book governed by DA-DOC-002. Canonical source remains under spec/src.

DA-GOV-001 — Canonical functionality

Requirement. Protected coordinator behavior MUST have concise canonical requirements and mapped source ownership before or with implementation changes.

Acceptance details

  • SUMMARY.md MUST index every canonical chapter.
  • Requirements MUST have unique DA-<AREA>-NNN identifiers, one normative statement and two to four acceptance bullets.
  • Planned rollout work MUST remain distinct from implemented and verified behavior.
  • Supporting records and generated books MUST NOT replace canonical authority.

DA-GOV-002 — Verification evidence

Requirement. Every requirement MUST have exactly one verification row with an allowed status and concrete evidence.

Acceptance details

  • Missing, duplicate or orphan requirement rows MUST fail validation.
  • Status MUST be Implemented, In progress or Planned.
  • Local, hosted and consumer qualification MUST be reported separately.

DA-GOV-003 — Spec-first and discovery

Requirement. Protected changes MUST update every mapped canonical owner, and unresolved change discovery or unmapped protected paths MUST fail closed.

Acceptance details

  • Local checks MUST use Jujutsu when available and Git otherwise; CI MUST inspect its complete source range.
  • Tests and generated artifacts MUST NOT stand in for owning chapter changes.
  • Maintainers MUST run pnpm spec:search before broad canonical scans; conceptual queries MAY use --semantic.
  • spec-validator doctor and QMD checks MUST verify host wiring without entering CI’s network-independent canonical checks.

DA-GOV-004 — Generated and private state

Requirement. Generated book output, QMD databases, operational reports, caches and credentials MUST remain outside tracked canonical source and public site input.

Acceptance details

  • Ignore rules MUST cover spec/book/, .qmd/index.sqlite*, reports/, .renovate/ and local state.
  • Only committed specification source MAY determine the public book.
  • Secrets, tokens, private API bodies and live report snapshots MUST NOT be copied into the book or its artifact.

DA-GOV-005 — Patched worker dependency resolutions

Requirement. The coordinator MUST use patched glob and minimatch resolutions while preserving the reviewed Renovate worker’s file-selection and cleanup contracts.

Acceptance details

  • Installed direct and transitive resolutions MUST use glob at least 14.0.2 and minimatch at least 11.0.1 for GHSA-3g3m-2fjr-6pw4 and GHSA-g3hv-75wg-m249 respectively.
  • Compatibility tests MUST exercise the actual Renovate matcher and the resolved glob/rimraf selection and bounded-cleanup behavior.
  • Other audit findings MUST remain visible without inheriting waivers from another repository or release.

Source change map

spec-validator.config.mjs is executable authority for path classification.

Protected areaCanonical owner
Discovery, registry closure, inventoryInventory
Repository/monitoring scopeRepository policy
Generated Renovate configuration / runnerReconciliation
Post-upgrade release intentRelease intent
Consumer workflows, wrappers and templatesConsumer integration
Audit and authentication detectorMonitoring
Profile validator and writerOrganization profile refresh
Notification entrypointRelease notifications
Hosted workflowsOwning function plus workflow wiring; check/Pages additionally govern specification delivery
Spec config, book/QMD wiring, guidance, repository checkerGovernance
Package manifest / lockfileGovernance and specification delivery

The repository uses the released Deno-free @lapismd/spec-validator range. pnpm verify retains formatter, syntax/workflow-pin checks and the complete functional test suite, then runs canonical validation, book build and spec-first. Rollout status-only edits in PLAN.md do not require unrelated canonical edits.

Wave planning/evidence/state/attention and their CLI entrypoints map to waves.md. The coordinator state branch is operational storage, never canonical book input.

The bounded public-file and sanitized HTTP-response modules share discovery’s Inventory and Repository policy owners under DA-INV-005/006. Their explicit map does not authorize new scopes or change operational rollout gates.

The wave pilot/recovery runbook is operational guidance linked from README; canonical wave requirements and workflow gates remain authoritative.

Tooling policy, runtime checks and qualification map to tooling.md. Expanded cohort evidence and its GET-only inspection entrypoint share that owner; ordinary validation rejects unsupported evidence and runtime claims. The ordinary repository checker validates the central contract as well as the version template, so a Deno-only or unreviewed template cannot silently enter normal verification. Registry qualification remains separate from offline tests.

The bounded PR-message renderer maps to reconciliation and profile requirements; operational previews and real source snapshots remain untracked.

Completion policy, verifier and reusable workflow are mapped to notifications and waves, with source-inventory isolation and explicit workflow wiring.

Tooling CI, provenance and refresh modules map to DA-TOOL-005/006 in the tooling chapter; selectors and source evidence grant no write or portability authority.

Publication verifier/transport/source observation and its policy map to publications.md. The reviewed Node runtime, owned setup-gh standard CLI pin and bundled public trust data do not change package manifests, lockfiles or advisory approval bindings. Public immutable crypto fixtures are test inputs, never operational snapshots or production fallback evidence.

Shared canonical-intake preparation and its immutable-source filesystem adapter map to release intent and consumer integration. Declarative source opt-ins add only exact reviewed canonical output paths; no executable consumer code or blanket main specification exemption is introduced. Workspace policy/fact/lock and bounded digest-slot formatting preparation share that mapping; the feature-specific slot module retains the existing public renderer export and grants no formatter, hook or output authority. Normal admission retains the separate dependency-wave/release-intent mapping.

The independent canonical development admission module maps to dependency waves and release intent. Its source-policy byte binding remains an internal inventory contract; Maintenance report and durable state schemas remain unchanged.

The channel policy/projection and static publisher reader map to publications and waves. Only source-reviewed cohort coordinates/scopes are committed; live proofs and operational artifacts remain ignored and outside public book uploads.

The completion observer feature module maps only to its existing notification and wave owners. Adding src/completion-observers.mjs does not introduce a catch-all protected-path exemption; DA-NOT-004 keeps held and excluded-source behavior explicit while preserving every dependency-write gate.

The separate default-empty SDK scope policy is checked alongside existing artifact policy before planning/configuration. DA-WAVE-009 maps scoped admission to wave/policy owners; its data grants no audit decision, source qualification, phase change or broad private dependency writer. Independent source guards and all ordinary candidate checks remain mandatory.

Public specification delivery

The source-qualified validator update uses released Node-only0.2.1 and its normal frozen registry lockfile. DA-DOC-001/002 retain the same verification, book-only artifact and Pages permission boundary. The changed dependency graph does not inherit the prior exact-lock advisory exception; writable automation remains held until that new binding has its own operator decision.

The public book is documentation. It does not publish operational reports or replace the repository’s source/deployment authorization boundaries.

DA-DOC-001 — Deterministic book source

Requirement. The specification book MUST build from indexed committed canonical Markdown with a pinned Node/pnpm/mdBook toolchain and the released Deno-free validator.

Acceptance details

  • Local and hosted validation MUST run the same pnpm verify entrypoint.
  • Frozen dependency installation MUST precede hosted verification.
  • QMD indexes and semantic model downloads MUST NOT be required by CI/book build.
  • Generated output MUST remain ignored rather than committed.

DA-DOC-002 — Restricted Pages deployment

Requirement. Pages deployment MUST publish only a successfully verified main-branch specification book through a separate minimal-authority deploy job.

Acceptance details

  • Pull requests MUST build/validate without Pages writes; manual publication MUST require main.
  • The upload path MUST be exactly spec/book, never the checkout, reports or arbitrary artifacts.
  • The build job MUST have read authority only; the deploy job MAY have only Pages and OIDC deployment writes.
  • Deployment MUST wait for successful verification/build and use the github-pages environment with serialized publication.

Build and deployment wiring

The book is hosted under the repository’s GitHub Pages project path. pages.yml builds the exact main revision, runs all checks, uploads its book-only artifact and deploys it. It does not read source secrets, mint a dependency App token, perform inventory/audit collection or enable dependency writes.

Book verification and reconciliation install the same frozen coordinator graph. DA-GOV-005 qualifies patched upstream glob/minimatch resolutions against the retained Renovate runner; Node, pnpm and mdBook pins remain independently fixed. An unchanged LOW deepmerge finding is not a clean full audit or a transferred exception from a consumer release.

Source and book checks also prepare the pinned standard GitHub CLI for offline public provenance regressions. It receives no credentials; only immutable test inputs and static public trust material enter those subprocesses.

Rollout and remaining work

Single-repository completion

The shared dependency workflow is qualified and enabled for Notebook after its genuine Core0.13.5 development intake, complete candidate/main CI, native auto-merge, Pages and repeated normal reconciliation. Other repositories remain independent adoption work. Notebook, Spec Validator, Visual Delta, Terminal, Registry, Plugins, Agent UI, AI, JJ Store, Notes and Server are source pilot policy entries; the first five have completed their applicable live/replay acceptance. Global phase stays pilot with hourly scheduling enabled. Promoting one reviewed entry from full to pilot enables that repository independently, without a global full rollout.

Server source103 is merged and its exact-main CI, hash-tagged image, Pages and normal completion callbacks pass. Per-entry eligibility retains its measured empty-note convention and all registry/migration/source/audit holds; full normal reconciliation and replay remain pending under adoption58.

Acceptance requires a genuine compatible Core update, shared canonical preparation, current PR and main qualification, source-owned version/release disposition, Pages, automatic completion/catch-up and idempotent repeat runs. A development-only update must retain no publication intent; it cannot stand in for evidence that an npm publication occurred. Existing genuine publication evidence and any unexercised release branch remain explicitly distinguished.

Remaining repository adoption belongs in separate assignable tasks with the same checklist, exact source evidence, repository-specific blockers and activation/rollback steps. Community, Nostr and Deno-only packages stay excluded.

Tracker50 now links sixteen separately assignable adoption tasks. The common adoption runbook defines source inspection, shared pins, independent qualification, per-entry activation, replay and rollback. The tracker records the completed pilot separately from remaining adoption; creating tasks does not enable writers.

The detailed maintenance plan owns delivery steps and dated receipts. This page explains scope without embedding live operational data in the public book.

SliceCurrent boundary
S1 Policy/authenticationShared monitoring, read-only audit/probes and the isolated scheduled profile writer are qualified. All eligible version writers have migrated and passed their main App/Changesets jobs; genuine Plugins and profile candidates also started CI and merged.
S2 Image churnShared signed producer/resolver is qualified in Plugins and Notes, including full warm/repeated-producer acceptance and Notes production deployment. Both obsolete image-pin PRs are closed.
S3 Dependency wavesNotebook proves compatible development intake, native auto-merge, current-main completion and repeat reconciliation; hourly single-pilot scheduling is enabled. Other consumer/release-chain adoption remains independently tracked.
S4 Maintenance integrationThe deployed app reads monitoring policy, waves and open issues and supports confirmed eligible batches. Real report parsing and a disposable live command/preflight test are qualified; visual review remains separate.
S5 Publication recoveryRegistry preparation and publication are separate. Immutable artifact reuse, unchanged replay and rejection before writer minting are hosted-qualified; a genuine three-plugin batch is deployed and its public signatures verified. Package publishers retain source authority.
S6 Tooling/driftNode CLI contracts, initial source cohorts, candidate guards, operational drift reporting and exact advisory admission are deployed. Additional cohorts and consumer whole-recipe guard adoption remain in progress.

No row in this table authorizes additional writes, activates a parked host or waives a product/audit gate. Current source qualification is recorded in the verification matrix; hosted and downstream evidence remains separate.

S6 now has a source implementation for Node-only version preparation, central cohort observations and candidate drift rejection. Hosted qualification and consumer adoption remain separate; existing frozen Deno host sources and all advisory exception rules remain unchanged.

S6b adds production maintenance drift reporting and exact coordinator advisory admission before dependency write planning and App minting. The earlier LOW decision is retired. The separately approved HIGH picomatch decision covered two exact runtime paths/source/lock bindings through November19,00:00UTC or sooner on a known fix; Issue71 owned remediation and retirement, and pilot success could not renew it. Those exact approvals are now retired after upstream withdrawal and zero-finding audit evidence, restoring the empty approval list. Consumer adoption and source-owner treatment of reported unknowns remain separate; a matching static check name is not complete qualification.

The bounded canonical-intake preparer and Notebook source opt-in are hosted qualified through44, including strict native committed-payload and unchanged consumer guard checks. The single-pilot evidence record retains exact source/run/state receipts and distinguishes the correct no-publication outcome from an actual npm release. Source verification still preserves unrelated peer edges and holds ambiguous contexts.

Successful same-source package recovery preserves retained signed artifacts and verifies existing registry bytes before resuming failed qualification. Automatic registry install-metadata readiness remains a concrete S5 maintenance follow-up; manual recovery is not completion of that automation. The bounded Notebook pilot under DA-WAVE-007 retains every unrelated publisher wait while qualifying only its source-authorized development patch. Other source profiles, publisher contracts and unsupported migrations remain independent adoption work.

The next small-repository slice registers Spec Validator’s existing Check workflow and Visual Delta’s existing CI, PR-specification, Pages and version workflows by exact IDs, paths and supported events. The read-only App probe adds only those two exact targets. Tag publishers, native capture, image publishers and callback self-triggers are not completion sources; verified npm notifications remain separate. Registration74 initially retained phase full for both repositories pending merged source acceptance and separate activation/replay, now recorded below. Spec Validator currently consumes no Lapis npm dependency; no synthetic Core pin or version recipe is introduced to create an update. Visual Delta consumes only the Deno-free specification tool in development and retains its existing audit and compare-only browser gates. The operator requests a final merge pass and gives standing approval for per-repository activation after passing source acceptance; advisory exceptions and global full rollout are not implied.

The operator-approved next activation adds only Spec Validator after its source7 mergedf3bab11837648045540bf7ef948503131dcab041 and main Check44174151693 passed. Read-only existing-App probe44173967888 passed. Its normal functional no-Lapis-input contract preserves the current zero-update graph; no Changesets writer, dependency bump, version/tag or publication is invented. Notebook remains the sole exercised dependency-writing consumer; all other entries and existing holds/exclusions remain unchanged, and global phase stays pilot. Actual completion, ordinary no-update settlement and repeat receipts are recorded in the source activation record; source registration alone is not claimed as a new publisher or multi-consumer update proof.

Spec Validator activation75 is deployed at8c71f71d. Exact-main checks, live Pages and completion-driven run44176226486 pass; its current sourcef3bab118 is qualified with no updates, holds or waits. The active no-op operation is unchanged, and durable state matches the hosted candidate. This is producer/ no-input adoption, not an invented dependency update or new package release. The owned source audit follow-up is Spec Validator8, separate from activation.

Ordinary replay44177306438 retains the same unchanged operation after the first post-activation run44176226486. Generations171→172 form the expected durable state chain and both published states match their hosted candidates. No dependency PR or package release is created; Spec Validator adoption62 is complete. Existing development-tool remediation remains separately tracked in Spec Validator8. At that Spec Validator handoff, fifteen repository adoptions remained open; Visual Delta is now completed below and fourteen adoption tasks remain open; this is not global full rollout.

Visual Delta adoption79 and activation77 are deployed after current source acceptance. Ordinary runs44182784733 and44182833366 qualify e755e2a0 with no updates, holds or waits, retain the same unchanged operation and form the verified durable state chain178→179. Exact source, Pages, artifact and state receipts are in the activation record. Notebook, Spec Validator, Visual Delta, Terminal and Registry are the pilot entries; other entries, exclusions, global phase and holds remain unchanged. Visual Delta’s independent guard admits only compatible Node-only validator0.2 development patches. No new dependency update or publisher execution is claimed.

VD-GOV-008 continues to gate audit remediation and package publication. The earlier blanket maintenance hold was too broad; the existing unapproved HIGH remains a publication blocker. This adoption does not change audit collectors, waive a finding, rebind an exception or authorize tags, uploads or baselines.

Visual Delta80 owns its separate publication audit remediation; completed adoption63 does not waive that finding. Docs21 and Tasks31 previously retained required audit failures that cleared after the same upstream advisory withdrawal.

Parallel completion pass

Thirteen eligible adoption tasks remain after excluding Agent Redaction64 under the operator’s any-Deno-package boundary. Independent source batches cover foundations/plugins, native/server packages and applications/registry. Docs and Tasks previously retained required Changesets/picomatch audit failures; those consumer findings cleared after upstream advisory withdrawal. The coordinator exception is retired to an empty approval list and cannot authorize consumer gates by inheritance. Only reviewed individual source acceptance permits the subsequent per-entry activation, ordinary settlement and replay.

Terminal and Registry activation

The operator’s standing post-merge approval promotes only Terminal and Registry from full to pilot after their current source/main/callback acceptance. All other phases, global pilot settings, exclusions, source holds and advisory bindings are unchanged. Exact evidence belongs in the activation record.

Terminal source27 merged50d1bb9f with qualified macOS CI, spec Pages and actual false version intent. Its independent Core0.13 development-patch guard qualifies the real released0.13.4→0.13.5 candidate, including the no-note full version recipe; the coordinator’s empty-Changeset flag remains unchanged. Registry source184 merged69d8c063, passes current Checks/signed publication and actual callbacks, and retains its private API0.1/no-version contract. Its upstream API publication wait remains binding; activation does not waive that prerequisite or claim an invented npm release. The live acceptance record now proves Terminal’s genuine Core update, current-main/no-intent completion, durable settlement and unchanged repeat. Registry’s qualified no-update repeat retains its API prerequisite and unexercised dependency-publication branch. These two adoption tasks may close; all other source work remains separate.

Plugins and Agent UI activation

The operator’s standing post-merge approval promotes only Plugins and Agent UI from full to pilot after exact-source, current-main and verified completion acceptance. Their existing empty-Changeset settings stay unchanged: each real version recipe correctly returns false intent without a forced empty note. All other phases, holds, exclusions, global pilot settings and exact advisory bindings remain unchanged. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; unavailable upstream publication floors are not waived, and no dependency update, version PR or publication is invented to force activity.

AI and JJ Store activation eligibility

Standing post-merge operator approval promotes only AI and JJ Store from full to pilot after independently green source adoption and whole-recipe acceptance. Both entries add the proven emptyChangeset: true capability: an actual managed empty note lets the source CLI classify supported development intake without inventing version or publication intent. Their real no-note macros alone do not prove the changed-candidate guard succeeds. The bounded activation receipt retains those separate controls and exact current-main observations.

This is eligibility, not a current-main qualification override. Pending or failed current CI, source/audit policy, ownership and publication prerequisites still hold actual writes and release-chain advancement. Existing seven pilot entries, every other empty-note setting, exclusions, holds and global pilot gates remain unchanged. Ordinary live reconciliation, exact settlement and repeat acceptance remain open until their own receipts exist. The user’s unrelated JJ Store main/release repair exclusion does not alter the collector or assert a pass.

Notes activation eligibility

Standing post-merge operator approval promotes only Notes from full to pilot after source155 merged with all required checks passing. Its existing measured emptyChangeset: true flag remains unchanged. Source policy limits supported inputs and preserves frozen hosts; publisher/channel/audit authority stays with the source. The activation record separates source acceptance, current-source release preparation and the live publication attempt. Pending current CI and upstream/publication waits continue to hold writers. Existing nine pilot entries, all other flags/holds/exclusions, empty artifact capabilities and global pilot/schedule settings are unchanged. Actual publication proof, ordinary live settlement and repeat remain required; policy eligibility alone does not complete adoption53.

Mira, Design Core, Tasks and Docs activation

Standing post-merge operator approval promotes only Mira, Design Core, Tasks and Docs from full to pilot after independently green source adoption, current-main checks and verified completion callbacks. Mira retains its existing emptyChangeset: true flag; the other three introduce no forced empty note. Desktop’s private-archive holdReason, every Deno/community/Nostr exclusion, every other phase/flag and global pilot settings remain unchanged. Active advisory approvals stay empty after the picomatch retirement. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; retained branch-ownership holds and upstream publication waits are not waived, and no dependency update, version PR or publication is invented to force activity.

Verification

RequirementStatusEvidence
DA-OWN-001ImplementedSource boundaries in src/, generated PR rules and tests/automerge.test.mjs; no npm publisher entrypoint.
DA-POL-001ImplementedloadAllowlist/loadPolicy in src/github.mjs; tests/github.test.mjs and tests/policy.test.mjs.
DA-POL-002ImplementedmonitoringRepositories; tests/maintenance-policy.test.mjs; qualified Maintenance policy adapter recorded in PLAN.md.
DA-POL-003ImplementedPolicy/consumer tests; real-snapshot full-phase exclusions and exact holds in2026-11-17-reviewed-cohorts-and-exclusions.md.
DA-INV-001ImplementedRevision-bound discoverRepository and duplicate-owner guard; tests/github.test.mjs.
DA-INV-002ImplementedRegistry-only availability closure and error semantics; tests/policy.test.mjs and tests/github.test.mjs.
DA-INV-003ImplementedPortability/onboarding/hold matrix in scripts/inventory.mjs; unpublished-private-consumer regression.
DA-INV-004ImplementedruntimeCycles and cycle-aware generated rules; SCC and update-policy cases in tests/policy.test.mjs.
DA-INV-005Implementedtests/github-public-files.test.mjs; exact-main44027266295 and accepted normal generations99/100 qualify bounded public transport.
DA-INV-006Implementedtests/github-public-files.test.mjs; sanitized failures pass; normal hosted recovery44027276770/44028620105 succeeds without attributing the old403 cause.
DA-REC-001ImplementedRestricted repositoryConfig plus central renovate.config.cjs; generated configuration validation.
DA-REC-002ImplementedCompatible/breaking Renovate rules; tests/automerge.test.mjs and tests/policy.test.mjs; repository merge rules remain external gates.
DA-REC-003ImplementedExplicit environment/variable gates in reconcile.yml, scripts/inventory.mjs and renovate.config.cjs.
DA-REC-004ImplementedPer-target permissions, one allowed command and environment whitelist; native artifact reporting regression retains errors without status-write authority.
DA-REL-001ImplementedBranch-context and exact frozen install in scripts/prepare-pr.mjs; generated post-upgrade contract.
DA-REL-002ImplementedreleaseIntent, private-root runtime detection without package intent even under private-package versioning, catalog handling and onboarding guard; exact production-hook coverage in tests/tooling.test.mjs.
DA-REL-003ImplementedwriteChangeset; repeated compatible-update and stale generated bump-to-empty retry regressions in tests/policy.test.mjs.
DA-INT-001ImplementedAuthor-based bot policy and retained aggregate lanes; tests/policy.test.mjs, tests/consumer.test.mjs.
DA-INT-002ImplementedScoped App template in templates/version-packages.yml; workflow/version tests. Consumer rollout remains separately pending.
DA-INT-003ImplementedDocker host context forwarding; standalone flat-worker regression in tests/consumer.test.mjs.
DA-INT-004ImplementedRepeatable integration and retained Dependabot security coverage; tests/consumer.test.mjs.
DA-NOT-001ImplementedSource/registry checks in scripts/notify.mjs; notification identity tests in tests/policy.test.mjs.
DA-NOT-002ImplementedReceiver validation, reusable notifier and scheduled recovery; policy tests and workflow wiring.
DA-MON-001ImplementedGET-only audit and partial-report retention tests; operational-drift tests cover sanitized observed Actions vars with exact workflow provenance.
DA-MON-002ImplementedDetector precedence and arbitrary-token negative cases in tests/maintenance-policy.test.mjs.
DA-MON-003ImplementedExact owner-map execution rejects excluded/arbitrary targets before minting; hosted probes retain one-repository read-only scope and no source checkout.
DA-PR-001ImplementedSeparate source-generation/publication jobs; tests/workflows.test.mjs; App-created hosted PR qualification.
DA-PR-002ImplementedvalidateProfile grammar/diff boundary and stale-source checks; tests/profile-writer.test.mjs.
DA-PR-003ImplementedHistory-preserving update, duplicate, manual repair and retained-branch tests in tests/profile-writer.test.mjs.
DA-PR-004ImplementedOrdered legacy handover, no blind write retries and orphan guard; profile writer tests and hosted replay.
DA-WIRE-001ImplementedExplicit source/workflow map and parsed tests cover the contents-read audit context; deployed book qualification is tracked separately.
DA-GOV-001ImplementedCanonical 35-requirement baseline, local validation and hosted check 43759765126 passed.
DA-GOV-002ImplementedSingle-ID matrix and original missing-row rejection; complete local/hosted spec validation passed.
DA-GOV-003ImplementedMapped source negative probe, doctor 11/11, actual QMD search and main spec-first acceptance.
DA-GOV-004ImplementedIgnore rules, book-only artifact regression and deployed output; public operational-report paths return 404.
DA-GOV-005In progressInstalled floors and API compatibility: tests/renovate-runtime.test.mjs; hosted checks pending.
DA-DOC-001ImplementedReleased Node validator, pinned mdBook, 42 tests and all three spec lanes; Pages book job 43759765158 passed.
DA-DOC-002ImplementedMain-only isolated deployment 7809666306 succeeded; all indexed chapters, navigation, CSS and JavaScript read back over HTTPS.
DA-WAVE-001Implementedtests/runtime-minimum-repair.test.mjs: retained minimum, native candidate and operation/replay gates; wave, catalog and compound regressions remain passing.
DA-WAVE-002ImplementedExact recovery/reconciliation negatives, immutable-tree/CAS gates and hosted normal153/154 durable acceptance/read-back; reviewed-channel observation across rolling-PR replacement, successor-run backfill and stale-policy rejection in tests/canonical-channel-admission.test.mjs; final-state operation/channel/publisher attention actions and exact public coordinates in tests/attention.test.mjs, tests/waves.test.mjs and spec/records/2026-11-20-current-attention-actions.md; published bytes do not imply republishing; no manual state edits.
DA-WAVE-003ImplementedSource qualification/ownership regressions distinguish expected push workflows and external gates from unrelated same-SHA manual/scheduled Actions; Notebook44 native auto-merge, full current-main acceptance and repeat153/154 without duplicates.
DA-WAVE-004Implemented80-test source qualification, wave/evidence/CAS regressions and production admission wiring; hosted pilot pending.
DA-TOOL-001In progresstests/tooling.test.mjs; Node-only generated fixture; hosted/consumer qualification pending.
DA-TOOL-002In progressSource/lock cohort observations and pairing regressions; production inventory integration.
DA-TOOL-003In progressguardToolingChange in prepare-pr; validator-pilot-cohort regressions admit only reviewed0.2.1 and retain runtime, integrity, major and cohort rejection.
DA-REC-005ImplementedNative-body preservation, escaped/bounded renderer and wave/CI qualification regressions in tests/pr-messages.test.mjs.
DA-PR-005ImplementedManaged profile context, maintainer-text preservation, ambiguous-marker and GET-only duplicate regressions in profile/message tests.
DA-TOOL-004In progressRevision/lock/CI bindings and recipe separation in tests/tooling-evidence.test.mjs; production inventory.
DA-OPS-001In progressOperational-drift regressions cover local composites, settings gaps and trusted activation context; hosted context read-back remains pending.
DA-OPS-002ImplementedAdvisory/preflight tests, November17 approval record and November19 retirement prove exact picomatch admission then stale-cleanup removal to an empty approval list without changing rejection controls
DA-OPS-003In progressInventory pre-admission audit and repeated pre-App preflight; read-only/state-only behavior preserved; hosted acceptance pending.
DA-NOT-003ImplementedStale/fork/unknown negatives plus actual Notebook PR/main callbacks verify before App minting and send source-bound completion wake-ups.
DA-NOT-004ImplementedExplicit held-observer, unchanged hold, excluded-root, exact Desktop workflow and unsupported publisher/event regressions in tests/completion-observers.test.mjs; source caller and hosted activation remain separate.
DA-WAVE-005ImplementedCallback settlement, pending-check timing and graph isolation tests; all four pilot callers and repeated Plugins dispatch are hosted-qualified (PLAN.md).
DA-WAVE-006ImplementedCompound/mixed release-floor and lock regressions plus the bound generation82 replay in spec/records/2026-11-17-scoped-publisher-retirement.md.
DA-TOOL-005In progressSource/job/attempt controls; reviewed cohort record binds Docs/Agent UI/Terminal/Mira jobs and16 same-source observations; hosted refresh pending.
DA-TOOL-006In progressGET-only refresh16/16 preserves ranges/provenance; reviewed twelve-constraint repair and full-phase exclusion proof; hosted refresh pending.
DA-TOOL-007In progressCI28: exact1→0,29 focused/301 full cases and frozen Core0.13.5 recipe proof; Notebook43 main CI/version guard pass at4484fe44.
DA-PUB-001ImplementedReal crypto/mutation/source/recovery tests plus reject-only claim preflight; full-inventory proof is recorded in spec/records/2026-11-17-publication-budget.md.
DA-PUB-002ImplementedCurrent-first collection, bounded shared 128 MiB/256-request budget and exhaustion/cache negatives; no App inventory credentials or source/channel relaxation.
DA-REL-004ImplementedSchema1 source, branch-note retry and zero-write rejection;40 focused/517 full tests plus real Server replay.
DA-REL-006ImplementedInactive two-key seeded SDK capability; immutable current no-op and genuine historical native update/frozen proof, strict non-SDK/private bindings, and real pinned Renovate extraction/artifact/post-task/commit regression. No live capability or private admission is granted.
DA-REL-005ImplementedWorkspace source/lock/format tests and ten unchanged legacy-bound cases; exact digest-style repeats plus real JJStore replay.
DA-WAVE-007ImplementedSource-bound admission regressions and hosted Notebook Core0.13.5 intake/auto-merge/main/replay; unrelated publisher/runtime waits remain held.
DA-PUB-003In progressScoped/transitive-peer and publication-floor controls remain; 88 focused channel/Profile cases and fresh Linux verifier inventory admit the current Notes cohort for Server: spec/records/2026-11-19-notes-channel-refresh.md. Hosted rollout/replay remains separate.
DA-PUB-005ImplementedActual0.2.9/0.2.7 pinned-crypto recovery fixture, original/recovered identity and adversarial controls; spec/records/2026-11-18-agent-ui-verification-recovery.md.
DA-PUB-004ImplementedHosted generation82 (43989934897) verifies all ten selected packages plus History against current source-bound static contracts; size/ID/signature negatives pass.
DA-WAVE-008ImplementedOriginal hold/scoped-channel proof plus the live five-of-seven Notes failure, repaired same-manifest isolation regression and retained selected-dependency negative: spec/records/2026-11-19-schema2-manifest-wait-isolation.md.
DA-WAVE-009In progressScoped SDK admission tests retain immutable authority, deferred private evidence and normal global/current-source gates; live grant remains empty.

Detailed bootstrap commands, failure counts and hosted handoff live in the specification/Pages qualification record.

Terminal and Registry adoption acceptance is recorded in the live replay receipt. Terminal qualifies genuine development intake through current-main completion, false publication intent and durable repeat; Registry qualifies an honest no-update repeat while preserving its API publication wait. These observations extend DA-WAVE-003/005/007 evidence without waiving another source’s gate.

Desktop held-observer registration and its unchanged write boundary are recorded in the bounded qualification receipt.

Plugins and Agent UI post-merge activation uses the independent source receipts; live reconciliation and repeat remain pending their actual observation.

AI and JJ Store’s source/flag qualification extends DA-POL-001/003 and DA-WAVE-003/004 without bypassing complete current-main CI or publication/source holds. Deployment, live settlement and repeat remain pending their actual observations.

Mira, Design Core, Tasks and Docs post-merge activation uses the independent source receipts; live reconciliation and repeat remain pending their actual observation.

Published source evidence and channels

Agent UI’s separate tagged-workspace profile under DA-PUB-005 preserves its existing publisher; it does not relax main-head completion or channel admission.

Publication observations are independent of update eligibility. The latest-only policy remains the default for candidate selection; observing a next-tagged version alone does not admit it or change registry tags.

The exact configured Profile source/integrity binding MAY retire its verified own publication wait. Direct Profile consumption MUST be restricted to Server’s root package.json runtime dependencies; every other repository, manifest path and dependency type remains forbidden. Its exact verified next pin changes no registry tag, release floor, canonical source guard or advisory policy.

The November18 reviewed cohort refresh binds API0.6.9, UI0.2.4, Workspace0.4.8 and Profile0.2.6 to the exact successful Notes538bb469 publication and immutable artifact. Origin attempt1 and same-byte verification recovery attempt2 remain distinct; file-explorer0.2.8, all consumer scopes and default latest are unchanged. The complete measured proof is retained in spec/records/2026-11-18-notes-cohort-recovery.md.

The November19 refresh advances only those four exact identities to the current Notes source: API0.6.10, UI0.2.6, Workspace0.4.9 and Profile0.2.7 at source2838c3dc. Fresh registry signatures, Sigstore provenance, source contracts, publisher artifact and attempt3 verification agree under the reviewed Linux x64 Node24.15.0/gh2.102.0 verifier. File Explorer0.2.8, consumer scopes and default latest remain byte-for-byte unchanged. The measured read-only proof and prospective Server admission are retained in spec/records/2026-11-19-notes-channel-refresh.md; hosted merge, writes, settlement and replay remain separate gates.

DA-PUB-001 — Verified publication identity

Requirement. Published-source acceptance MUST bind package/version/integrity to authenticated provenance, the reviewed public publisher workflow and exact successful source qualification.

Acceptance details

  • Registry signatures and Sigstore provenance MUST verify with the reviewed runtime trust material, exact signer identity, issuer, certificate source/invocation and subject digest; gitHead alone MUST NOT qualify publication and the npm publish statement MUST supply consistency only, with structurally inconsistent claims rejected before tarball downloads and preflight never granting verified assurance.
  • Exact public source/package contracts and publisher release-manifest/tarball hashes MUST agree; recovery MAY supply successful post-publication verification only for the same source and immutable bytes.
  • Complete current source workflow/check/status coverage, exact run attempts and the publisher’s qualification/publication/verification gates MUST remain required; unknown or mismatched evidence MUST remain held.
  • Newer-release baselines, required dependency floors, compound-contract rules, current-main acceptance and operation CAS MUST remain unchanged.

DA-PUB-002 — Bounded read-only normalization

Requirement. Publication evidence MUST be normalized independently of version eligibility through bounded read-only observation without executing candidate data.

Acceptance details

  • Current public owned versions MUST receive a collection pass before other tag and retained-baseline probes, independently of latest eligibility; channel-not-admitted and provenance-unknown MUST remain explicit independent reasons.
  • Exact Node runtime, owned setup action, standard GitHub CLI binary and static public trust-seed bytes MUST match the reviewed contract before verification; missing, changed or unsupported tools MUST fail closed without installing replacements or changing the approved package graph; bundled npm Sigstore JavaScript MUST NOT execute.
  • Fetches MUST retain a shared 128 MiB total-byte and 256-request budget plus bounded per-response size, timeouts, redirects and archive inflation; source visibility MUST precede source/artifact reads, existing read-only public-source authority MUST be reused without App minting or added permissions, and no candidate scripts, signing credentials or private API bodies may enter execution or public state.
  • Versioned receipts MAY persist only normalized public coordinates/digests and assurance, never raw bundles/artifacts; legacy state remains readable and persisted facts never replace fresh channel/current-head checks and prior verified receipts MUST remain available after unknown fresh observations.

DA-PUB-003 — Reviewed channel cohort

Requirement. Wave mode MAY admit only exact reviewed channel identities within explicit active consumer scopes; default and flat reconciliation MUST remain latest-only.

Acceptance details

  • Source policy MUST bind each package, version, integrity, public publisher and attested source; fresh channel, verified publication and exact source-contract evidence MUST agree.
  • Direct admission MUST match repository, manifest path and dependency type, with Profile restricted to Server’s root runtime dependencies; consumer prerequisite closure MUST remain rooted in that path’s approved seeds, and public owned publisher retirement MAY use only approved actual runtime/optional/peer fields and their freshly verified cohort prerequisites, with direct scope filters and global eligibility unchanged.
  • Unknown policy, missing scope, deprecated or moved channel, incomplete proof and changed identity MUST fail closed; immediate target revalidation MUST refresh registry identities before consumer writes.
  • Raw publication channel facts MUST remain unchanged; reports MUST retain remaining channel, source, release-floor, compatibility and ownership holds, with unchanged durable/report schemas and CAS.

DA-PUB-004 — Static plugin publisher proof

Requirement. Plugins static publication MUST use its separate reviewed workflow, environment, job and artifact contract with authenticated npm provenance and exact published-byte agreement.

Acceptance details

  • Exact successful public nonfork main workflow/run/attempt and all current source qualification MUST agree with the authenticated certificate, registry signature, subject digest and source package contract.
  • The runtime plugin ID/version MUST come from the public source manifest returned as a file at the attested commit, with package directory/release tag and runtime ID/archive coordinates remaining distinct and source/signature-bound.
  • The immutable candidate MUST bind package/version, plan, manifest, tarball digest/size and registry bytes within the static profile’s 64 MiB ZIP/aggregate inflation, 16 MiB npm archive, 8 MiB plugin archive/signed file and 32 MiB nested inflation caps, retaining release/path bounds and rejecting ambiguous, expired, mismatched or different-byte skip evidence.
  • The reader and cryptographic verifier MUST share the static profile’s 16 MiB npm archive bound only for the reviewed Plugins publisher, reject unreviewed profiles and retain Notes’ existing 8 MiB artifact/4 MiB tarball/32 MiB inflation bounds plus the shared total fetch-byte, request, source and recovery gates without candidate execution, signer access or publisher writes.

DA-PUB-005 — Tagged workspace publisher proof

Requirement. Agent UI publication MUST use a separate reject-by-default tagged-cohort contract for its existing npm publisher, authenticated through the unchanged standard verifier.

Recovery is supported only for the immediately following attempt of the same origin run, after original prepare and both publishes succeeded and actual post-publication verification failed. Fresh latest and exact-attempt responses must bind the same repository, source, tag-push and reviewed workflow. Projected successful prepare/publish jobs must retain original timestamps and step evidence; virtual job IDs alone establish no republish. Repacking, republishing, reused verification, lost origin proof, incomplete coverage, unsupported later attempts and different-run recovery fail closed. Artifact creation remains within original prepare, with origin publication and recovered verification identities distinct.

Acceptance details

  • Only repository lapismd/agent-ui, workflow400453743 at .github/workflows/npm-publish.yml with its exact reviewed source-byte hash, tag-push provenance and npm-production certificate environment qualify; the exact stable tag must equal the attested source Agent UI package version, without accepting branch, dispatch or arbitrary tag fallbacks.
  • Both exact public source packages and unequal versions must match the original three-file artifact schema, SHA256 artifact identity, source-bound manifest, each SHA512 tarball and fresh official registry bytes; missing, extra, duplicate, different-byte or expired evidence fails closed under existing archive bounds.
  • Successful original prepare, both version-specific publishes and original or bounded recovered verification MUST remain required with distinct attempt identities, original artifact timing and complete source CI/status coverage, current contract, ancestry and unchanged cryptographic issuer/signer/source/subject/registry checks.
  • This profile grants no publication, tag mutation, new key, credential or completion authority; Notes/static profiles, channel floors, budgets and main-head completion remain unchanged, and an unsupported or unexercised publisher cannot become verified by registration alone.