@timurproko/a1 0.1.8-dev.436 → 0.1.8-dev.443

package/dist/foundation/startup/index.d.ts

@@ -1 +1,2 @@
+export * from "./startup-budget.js";
 export * from "./startup-runtime.js";

package/dist/foundation/startup/index.js

@@ -1 +1,2 @@
+export * from "./startup-budget.js";
 export * from "./startup-runtime.js";

package/dist/foundation/startup/startup-budget.d.ts

@@ -0,0 +1,46 @@
+import type { StartupTraceEvent } from "./startup-runtime.js";
+export interface StartupPerformanceEvidence {
+    readonly profileId: "a1" | "pi";
+    readonly launchKind: "post-update" | "no-live-supervisor" | "warm";
+    readonly events: readonly StartupTraceEvent[];
+    readonly moduleGraph?: {
+        readonly loadedFiles: number;
+        readonly evaluatedBytes: number;
+        readonly groups: readonly {
+            readonly group: string;
+            readonly files: number;
+            readonly evaluatedBytes: number;
+        }[];
+    };
+}
+export interface StartupBudgetViolation {
+    readonly profileId: "a1" | "pi";
+    readonly launchKind: "post-update" | "no-live-supervisor" | "warm";
+    readonly elapsedMs: number;
+    readonly budgetMs: number;
+    readonly dominantPhases: readonly {
+        readonly phase: string;
+        readonly durationMs: number;
+    }[];
+    readonly moduleGraph?: StartupPerformanceEvidence["moduleGraph"];
+}
+/** Resolve the declared budget for one launch kind so measurement and reporting never restate the numbers. */
+export declare function resolveStartupBudgetMs(launchKind: StartupPerformanceEvidence["launchKind"], budgets?: {
+    readonly postUpdateMs: number;
+    readonly noSupervisorMs: number;
+    readonly warmMs: number;
+}): number;
+/** Compare measured startup evidence with its budget without deciding whether the channel enforces it. */
+export declare function evaluateStartupPerformanceBudget(evidence: StartupPerformanceEvidence, budgets?: {
+    readonly postUpdateMs: number;
+    readonly noSupervisorMs: number;
+    readonly warmMs: number;
+}): StartupBudgetViolation | null;
+/** Render one budget violation as the single message used by failures, evidence, and run summaries. */
+export declare function formatStartupBudgetViolation(violation: StartupBudgetViolation): string;
+/** Enforce the startup budget in a channel that fails on an overrun. */
+export declare function assertStartupPerformanceBudget(evidence: StartupPerformanceEvidence, budgets?: {
+    readonly postUpdateMs: number;
+    readonly noSupervisorMs: number;
+    readonly warmMs: number;
+}): void;

package/dist/foundation/startup/startup-budget.js

@@ -0,0 +1,42 @@
+const STARTUP_PERFORMANCE_BUDGETS = { postUpdateMs: 2_000, noSupervisorMs: 2_500, warmMs: 2_000 };
+/** Resolve the declared budget for one launch kind so measurement and reporting never restate the numbers. */
+export function resolveStartupBudgetMs(launchKind, budgets = STARTUP_PERFORMANCE_BUDGETS) {
+    return launchKind === "warm" ? budgets.warmMs : launchKind === "no-live-supervisor" ? budgets.noSupervisorMs : budgets.postUpdateMs;
+}
+/** Compare measured startup evidence with its budget without deciding whether the channel enforces it. */
+export function evaluateStartupPerformanceBudget(evidence, budgets = STARTUP_PERFORMANCE_BUDGETS) {
+    const events = [...evidence.events].sort((left, right) => left.elapsedMs - right.elapsedMs);
+    const ready = events.findLast(event => event.phase === "first-input-ready-render");
+    // Invariant: a launch that never became input-ready is a functional failure rather than a
+    // timing observation, so it throws in every enforcement mode instead of being recorded.
+    if (!ready)
+        throw new Error(`startup budget failed for ${evidence.profileId}: first input-ready render was not recorded`);
+    const budgetMs = resolveStartupBudgetMs(evidence.launchKind, budgets);
+    if (ready.elapsedMs <= budgetMs)
+        return null;
+    const intervals = events.map((event, index) => ({
+        phase: event.phase,
+        durationMs: event.elapsedMs - (events[index - 1]?.elapsedMs ?? 0),
+    })).sort((left, right) => right.durationMs - left.durationMs);
+    return {
+        profileId: evidence.profileId,
+        launchKind: evidence.launchKind,
+        elapsedMs: ready.elapsedMs,
+        budgetMs,
+        dominantPhases: intervals.slice(0, 3),
+        ...evidence.moduleGraph === undefined ? {} : { moduleGraph: evidence.moduleGraph },
+    };
+}
+/** Render one budget violation as the single message used by failures, evidence, and run summaries. */
+export function formatStartupBudgetViolation(violation) {
+    const graph = violation.moduleGraph === undefined ? ""
+        : `; module graph: ${violation.moduleGraph.loadedFiles} files, ${violation.moduleGraph.evaluatedBytes} evaluated bytes (${violation.moduleGraph.groups.map(group => `${group.group} ${group.files}/${group.evaluatedBytes}`).join(", ")})`;
+    const phases = violation.dominantPhases.map(item => `${item.phase} ${Math.round(item.durationMs)}ms`).join(", ");
+    return `startup budget failed for ${violation.profileId} ${violation.launchKind}: ${Math.round(violation.elapsedMs)}ms exceeds ${violation.budgetMs}ms; dominant phases: ${phases}${graph}`;
+}
+/** Enforce the startup budget in a channel that fails on an overrun. */
+export function assertStartupPerformanceBudget(evidence, budgets) {
+    const violation = evaluateStartupPerformanceBudget(evidence, budgets);
+    if (violation)
+        throw new Error(formatStartupBudgetViolation(violation));
+}

package/dist/foundation/startup/startup-runtime.d.ts

@@ -1,19 +1,5 @@
 import { PRODUCT_IDENTITY } from "../../product-identity.js";
 export type StartupPhase = "command-invoked" | "bootstrap-start" | "bootstrap-selected" | "durable-validation-start" | "durable-validation-complete" | "replacement-supervisor-start" | "replacement-supervisor-ready" | "guardian-start" | "guardian-connected" | "ui-entry" | "ui-modules-loaded" | "pi-services" | "resource-discovery" | "session-created" | "settings-loaded" | "first-input-ready-render";
-export interface StartupPerformanceEvidence {
-    readonly profileId: "a1" | "pi";
-    readonly launchKind: "post-update" | "no-live-supervisor" | "warm";
-    readonly events: readonly StartupTraceEvent[];
-    readonly moduleGraph?: {
-        readonly loadedFiles: number;
-        readonly evaluatedBytes: number;
-        readonly groups: readonly {
-            readonly group: string;
-            readonly files: number;
-            readonly evaluatedBytes: number;
-        }[];
-    };
-}
 export interface StartupTraceEvent {
     readonly schema: typeof PRODUCT_IDENTITY.evidence.startupTraceSchema;
     readonly traceId: string;
@@ -38,9 +24,4 @@ export declare function enableStartupCompileCache(dataDir: string, releaseId: st
 export declare function startupCompileCachePath(dataDir: string, releaseId: string | null, dependencyLayerIds: readonly string[]): string;
 /** Retain current compile namespaces plus a bounded number of recent fallbacks. */
 export declare function collectCompileCaches(dataDir: string, protectedPaths: readonly string[], keepRecent?: number): Promise<void>;
-export declare function assertStartupPerformanceBudget(evidence: StartupPerformanceEvidence, budgets?: {
-    readonly postUpdateMs: number;
-    readonly noSupervisorMs: number;
-    readonly warmMs: number;
-}): void;
 export declare function parseStartupTrace(source: string): readonly StartupTraceEvent[];

package/dist/foundation/startup/startup-runtime.js

@@ -97,28 +97,6 @@ export async function collectCompileCaches(dataDir, protectedPaths, keepRecent =
             await rm(candidate.path, { recursive: true, force: true });
     }
 }
-export function assertStartupPerformanceBudget(evidence, budgets = {
-    postUpdateMs: 2_000,
-    noSupervisorMs: 2_500,
-    warmMs: 2_000,
-}) {
-    const events = [...evidence.events].sort((left, right) => left.elapsedMs - right.elapsedMs);
-    const ready = events.findLast(event => event.phase === "first-input-ready-render");
-    if (!ready)
-        throw new Error(`startup budget failed for ${evidence.profileId}: first input-ready render was not recorded`);
-    const budget = evidence.launchKind === "warm"
-        ? budgets.warmMs
-        : evidence.launchKind === "no-live-supervisor" ? budgets.noSupervisorMs : budgets.postUpdateMs;
-    if (ready.elapsedMs <= budget)
-        return;
-    const intervals = events.map((event, index) => ({
-        phase: event.phase,
-        durationMs: event.elapsedMs - (events[index - 1]?.elapsedMs ?? 0),
-    })).sort((left, right) => right.durationMs - left.durationMs);
-    const graph = evidence.moduleGraph === undefined ? ""
-        : `; module graph: ${evidence.moduleGraph.loadedFiles} files, ${evidence.moduleGraph.evaluatedBytes} evaluated bytes (${evidence.moduleGraph.groups.map(group => `${group.group} ${group.files}/${group.evaluatedBytes}`).join(", ")})`;
-    throw new Error(`startup budget failed for ${evidence.profileId} ${evidence.launchKind}: ${Math.round(ready.elapsedMs)}ms exceeds ${budget}ms; dominant phases: ${intervals.slice(0, 3).map(item => `${item.phase} ${Math.round(item.durationMs)}ms`).join(", ")}${graph}`);
-}
 export function parseStartupTrace(source) {
     const events = source.split(/\r?\n/).filter(Boolean).map(line => JSON.parse(line));
     for (const event of events) {

package/dist/native/darwin-arm64/manifest.json

@@ -5,7 +5,7 @@
   "platform": "darwin",
   "architecture": "arm64",
   "capability": "supported",
-  "builtAt": "2026-09-16T16:00:56.139Z",
+  "builtAt": "2026-09-16T18:44:13.029Z",
   "artifact": {
     "filename": "process-guardian",
     "sha256": "9db1726bbe3fc2e8292f2ead1e7e9d0fd4d7d0dc9217b372582bf354b0f565dc",

package/dist/native/linux-x64/manifest.json

@@ -5,7 +5,7 @@
   "platform": "linux",
   "architecture": "x64",
   "capability": "supported",
-  "builtAt": "2026-09-16T16:00:53.100Z",
+  "builtAt": "2026-09-16T18:44:05.437Z",
   "artifact": {
     "filename": "process-guardian",
     "sha256": "d8cda6b0c7cb36c0cc41e90802aceebf6c02eaebbc08a83d7d963d2e918dbd7a",

package/dist/native/win32-x64/manifest.json

@@ -5,10 +5,10 @@
   "platform": "win32",
   "architecture": "x64",
   "capability": "supported",
-  "builtAt": "2026-09-16T16:01:51.175Z",
+  "builtAt": "2026-09-16T18:44:34.962Z",
   "artifact": {
     "filename": "process-guardian.exe",
-    "sha256": "6a50d218059b28154f0a1727b80e670fa478ef3f25b6e2f5780f60addfe83fc7",
+    "sha256": "47b347f1a5782f17d232cf3e2619fdba4c91a96427d931b2a9b716b888c7470d",
     "size": 177664
   },
   "provenance": {

package/docs/local-worktree-cleanup.md

@@ -1,8 +1,8 @@
 # Local worktree cleanup after verified delivery
 
-Local cleanup completes the delivery order in [the archive runbook](openspec-archive-automation.md). For version 3 that is one authorized manual implementation/acceptance/archive merge, read-only verification, remote topic-ref deletion, then safe local cleanup. Legacy versions still require their applicable acceptance-record and automatic archive merges. GitHub Actions never reaches into a developer machine. This command neither publishes archives nor merges PRs or deletes remote refs.
+Local cleanup completes the delivery order in [the archive runbook](openspec-archive-automation.md). For version 3 that is one authorized manual implementation/acceptance/archive merge, read-only verification, remote topic-ref deletion, then safe local cleanup. Legacy versions still require their applicable acceptance-record and automatic archive merges. GitHub Actions never reaches into a developer machine. Local cleanup never publishes archives or merges PRs; `complete`, preview, and queue/watch do not delete remote refs, while explicitly confirmed closed-unmerged `discard` owns only its exact expected-SHA topic-ref deletion.
 
-The implementation is repository tooling, not part of the installed A1 product. It requires Node, Git, and GitHub read access. No product build, dependency installation, interactive UI, or OS-service provisioning is needed. It supports this repository's `origin` on github.com, via HTTPS or SSH.
+The implementation is repository tooling, not part of the installed A1 product. It requires Node, Git, and GitHub read access; the explicit closed-unmerged discard operation additionally requires authenticated permission to delete its exact remote topic ref. No product build, dependency installation, interactive UI, or OS-service provisioning is needed. It supports this repository's `origin` on github.com, via HTTPS or SSH.
 
 ## Standard completed-delivery command
 
@@ -18,10 +18,27 @@ node scripts/governance/local-worktree-cleanup.mjs complete \
 
 `complete` is explicit cleanup authorization for that exact candidate. It creates and releases an exact registration when needed, applies the repository-owned generated-path policy, verifies live merge/archive/CI/ref evidence, evaluates only that candidate, uses journaled non-force Git removal, deletes only the unchanged local topic ref, and leaves persistent watcher authority unchanged. Repeating it reports the completed candidate as already absent. Existing conflicting ownership, identity drift, unavailable evidence, or unknown content remains blocking.
 
-The central disposable policy is `node_modules`, `dist`, `.builds`, `.artifacts/openspec-archive`, and `.artifacts/validation`. The last root contains repository-generated validation selection and result reports. Each encountered path must be ignored and stay inside the exact worktree with no link, special file, or nested repository boundary. Authority is component-exact: `.artifacts`, sibling directories such as `.artifacts/other`, and near matches such as `.artifacts/validation-user` remain blocking. Tracked/staged/unstaged/untracked content and every unknown ignored path still block. A tracked regular `.gitmodules` file alone is ordinary content; actual nested `.git` metadata, gitlinks, configured submodules, and submodule changes block. Ordinary content and these approved generated roots are traversed under separate finite entry allowances, so a normal dependency installation does not consume the ordinary source-tree allowance; both allowances retain the same deadline and content-boundary checks.
+The central disposable policy is `node_modules`, `dist`, `.builds`, `.artifacts/openspec-archive`, `.artifacts/validation`, `native/process-guardian/target`, and `native/terminal-host/target`. The artifact roots contain repository-generated finalization and validation reports; the two native roots contain repository-generated Cargo output. Each encountered path must be ignored and stay inside the exact worktree with no link, special file, or nested repository boundary. Authority is component-exact: `.artifacts`, sibling directories such as `.artifacts/other`, near matches such as `.artifacts/validation-user`, arbitrary `target` directories, and sibling native projects remain blocking. Tracked/staged/unstaged/untracked content and every unknown ignored path still block. A tracked regular `.gitmodules` file alone is ordinary content; actual nested `.git` metadata, gitlinks, configured submodules, and submodule changes block. Ordinary content and these approved generated roots are traversed under separate finite entry allowances, so a normal dependency installation does not consume the ordinary source-tree allowance; both allowances retain the same deadline and content-boundary checks.
 
 Agents do not manually remove generated content, call `git worktree remove`, or delete the local branch after delivery. The JSON result is authoritative: report success only for `removed` or verified `already-absent`; otherwise retain the worktree and report the exact blocker. Legacy roles can supply separate `--source-pr`, `--candidate-pr`, and `--role` values.
 
+## Explicit closed-unmerged discard
+
+Closing a PR does not itself authorize deletion. After the maintainer explicitly rejects one exact PR and separately confirms remote deletion, run the candidate-scoped command from the primary checkout:
+
+```bash
+node scripts/governance/local-worktree-cleanup.mjs discard \
+  --repo D:/Git/a1 \
+  --path D:/Git/a1/.worktrees/rejected-task \
+  --change rejected-change \
+  --pr 123 \
+  --confirm-closed-unmerged
+```
+
+`discard` requires the named PR to remain closed without merge, target `develop`, belong to this repository, and identify the exact registered worktree HEAD and branch. It first applies the same clean-content and generated-root inspection used by `complete`. It then verifies the remote topic branch is unprotected, non-reserved, and still equals the PR head; deletes only that ref with an expected-SHA lease; verifies remote absence; rechecks the local candidate; removes the worktree non-forcibly; and atomically deletes only the unchanged local branch.
+
+An open, merged, reopened, forked, protected, reserved, advanced, dirty, active, linked, nested, replaced, current, or unverifiable candidate remains blocking. Remote deletion followed by a Windows lock or later local blocker is reported as `partial`; the journal preserves the remaining worktree/local ref for the same exact confirmed command to inspect and resume. The command never scans by age or name, adopts another session's checkout, enables queue/watch, or turns PR close events into automatic discard authority.
+
 ## Preview first
 
 From a checkout containing the reviewed tooling:

package/docs/openspec-archive-automation.md

@@ -214,7 +214,7 @@ After version-3 merge, verify:
 
 Only then shall the owning agent invoke the exact-candidate `complete` operation documented in [local cleanup](local-worktree-cleanup.md) from the primary checkout. The command owns registration/release, repository-generated disposables, one bounded evidence pass, non-force worktree removal, and unchanged local-ref cleanup; agents do not manually delete generated content, worktrees, or branches. Version 3 uses the implementation PR as both source and candidate and does not wait for nonexistent acceptance/archive PRs.
 
-Closing an unmerged PR does not authorize local or remote deletion. Remote cleanup deletes only the exact unchanged same-repository unprotected topic ref and never touches local worktrees.
+Closing an unmerged PR does not by itself authorize local or remote deletion. After explicit candidate-specific rejection and remote-deletion confirmation, the repository-owned local `discard` command may compare-and-delete only that closed-unmerged PR's exact unchanged same-repository unprotected topic ref, then apply the ordinary non-force local safeguards. Automatic remote cleanup remains merge-only and never touches local worktrees.
 
 ## Legacy delivery
 

package/docs/validation.md

@@ -44,6 +44,23 @@ A build receipt binds checkout head, complete build inputs, toolchain, emitted f
 
 Npm download bytes may be reused with integrity checks and `--prefer-offline`, with normal network fallback. Every installation prefix remains fresh. Installed package trees, dependency certification, startup/profile state, mutable fixture repositories, passing outcomes, and publication evidence are never restored from caches.
 
+## Startup budget enforcement
+
+The exact-package startup gate always measures both profiles and all three launch kinds on the first attempt and never retries a measurement. `STARTUP_BUDGET_ENFORCEMENT` decides only what a timing overrun does:
+
+| Value | Where | Effect |
+| --- | --- | --- |
+| `record` | Development publication (`release.yml` with `mode == 'develop'`) and the pull-request `startup` group in `ci.yml` | Keeps the measurement, appends the violation to the evidence, emits a `::warning::` annotation, and lets the run succeed. |
+| `fail` | Nightly and stable publication, and Full regression | Throws the same message as before and blocks publication. |
+
+Any absent, empty, or unrecognized value means `fail`, so a local run and a misspelled channel both keep enforcing. A launch that records no input-ready frame fails in either mode, because that is a functional failure rather than a timing observation.
+
+`STARTUP_PERFORMANCE_RESULT` names the `a1-startup-performance-evidence-v1` file. It carries `enforcement`, `budgetViolations`, and one measurement per profile and launch kind with its `elapsedMs` and `budgetMs`. Publication lanes upload it as `release-validation-<version>-<platform>` next to the tier outcome and render it as a table in the run summary.
+
+The budget numbers themselves live in one place, `src/foundation/startup/startup-budget.ts`, and are declared by the `a1-shell` capability. Do not restate them in a workflow.
+
+To make development publication enforce budgets again, set `STARTUP_BUDGET_ENFORCEMENT: fail` in the `release.yml` validation step; rollback must not remove the measurement, the evidence fields, or the nightly and Full regression enforcement.
+
 ## Evidence inspection
 
 Download these artifacts from the exact workflow run:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timurproko/a1",
-  "version": "0.1.8-dev.436",
+  "version": "0.1.8-dev.443",
   "description": "Standalone terminal workspace for supervised native and managed agents",
   "type": "module",
   "privateLaunchContract": "neutral-launch-v1",