software-defence-factory 0.9.0 → 0.9.1

package/docs/npm.md

@@ -71,6 +71,43 @@ rebuilding the shared tag cannot remove an existing installation's pinned image.
 These retained images are recovery data; remove them only after confirming no
 installation or retained attempt needs them.
 
+## Protected evidence compatibility
+
+0.9.1 recognizes version-1 execution profiles emitted by native **0.8.0,
+0.9.0 and 0.9.1**. This is an exact allowlist in
+`factory/execution-profile.mjs`, independent of the installed package version;
+it is not a semver range or an automatic promise for later releases. Unknown
+runtime strings, unknown profile formats and incomplete legacy acceptance
+remain unverified or blocked. New profiles still record the actual emitting
+runtime version. Updates never relabel profiles, rewrite policy hashes,
+re-approve jobs or retry old work.
+
+Compatibility only permits interpreting the protected evidence. Publication
+still requires exact protected-file/run-record equality, successful linked
+phases with supported role/model provenance, the unchanged effective policy
+hash, retained source and candidate/patch identity, passing checks, independent
+review and bound approval. Synthetic or missing provenance cannot authorize
+publication. Enabled browser verification still requires current tool, story,
+candidate, attempt and retained artifact evidence; enabling or changing that
+policy invalidates prior evidence. CLI, API and dashboard consume the same
+delivery capability.
+
+Before extending this list, inspect the released profile/evidence writers and
+exercise both capability derivation and publication validation. Remove support
+for an older writer whenever a trust-relevant format, isolation, provenance or
+validation change makes its guarantees insufficient for current policy; bump
+the evidence format when its meaning changes. A package version bump alone is
+neither a reason to discard evidence nor proof of compatibility. Retain
+unsupported records unchanged and obtain fresh applicable evidence through the
+normal workflow; never repair them by editing private records or hashes.
+
+After native Verify/Review, the lead must qualify the installed patch read-only
+against actual retained production evidence. This source change and its
+controlled fixtures do not supply that proof. An already delivered PR keeps
+read-only receipt reconciliation. New publication still requires the current
+remote target to equal the original accepted base; checkpoint continuation and
+target mismatch remain the separate #42 limit.
+
 ## Release flow
 
 `.github/workflows/ci.yml` tests pull requests and pushes on Node 22 and 24,

package/docs/recovery.md

@@ -126,6 +126,16 @@ proof of the model/provider that served inference. Changing the installation's
 profile affects subsequent attempts, never the recorded history. A changed
 check/review policy still invalidates acceptance of earlier proof.
 
+Protected delivery evidence uses an explicit [runtime compatibility
+contract](npm.md#protected-evidence-compatibility): version-1 profiles from
+0.8.0, 0.9.0 and 0.9.1 can be interpreted by 0.9.1 while every existing trust
+and current-policy guard still applies. An upgrade alone does not require
+re-approval. Preserve original runtime versions, hashes and phase records;
+do not normalize old configuration or manufacture provenance to unblock a job.
+Unknown formats/versions remain blocked. Published PR receipt reconciliation
+stays read-only, and compatibility does not relax the original-base/remote-target
+guard or add checkpoint continuation.
+
 Attempts made before this metadata existed display **Not recorded
 (legacy/unknown)**. Do not copy today's profile onto them. For an investigation,
 compare the retained per-attempt measurement, logs, candidate/check/review hashes

package/factory/delivery.mjs

@@ -3,9 +3,8 @@ import { existsSync, lstatSync, mkdirSync, mkdtempSync, readFileSync, rmSync, wr
 import { join, resolve } from 'node:path';
 import { spawnSync } from 'node:child_process';
 import { isDeepStrictEqual } from 'node:util';
-import { VERSION } from './updates.mjs';
 import { configAt, digest } from './lib.mjs';
-import { effectiveExecutionConfig } from './execution-profile.mjs';
+import { effectiveExecutionConfig, isSupportedExecutionProfile } from './execution-profile.mjs';
 import { publicSourceAdmission } from './source-admission.mjs';
 import { QueueError } from './queue.mjs';
 import { readProjectLinks } from './project-links.mjs';
@@ -221,8 +220,8 @@ function trustedExecutionProfile(state, job, run, phase, expectedPolicy) {
         && ['explicit', 'provider_default'].includes(profile.modelSelection)
         && (profile.modelSelection === 'explicit' ? typeof profile.requestedModel === 'string' : profile.requestedModel === null)
       : profile.executor === 'deterministic' && profile.modelSelection === 'not_applicable' && profile.requestedModel === null;
-    return profile.version === 1 && profile.phase === phase && executorMatches
-      && profile.runtimeVersion === VERSION && profile.policyHash === expectedPolicy
+    return isSupportedExecutionProfile(profile) && profile.phase === phase && executorMatches
+      && profile.policyHash === expectedPolicy
       && isDeepStrictEqual(run.execution, profile);
   } catch { return false; }
 }
@@ -284,7 +283,7 @@ function acceptanceSummary(job, state, config, sourceAdmission) {
     { build: buildRun, verify: checkRun, review: reviewRun, handoff: handoffRun }, candidate, checks, review);
   if (!phaseEvidence.trusted) return { state: 'blocked', reason: phaseEvidence.reason };
   const validRun = (run, command) => run?.command === command && run.state === 'succeeded' && run.outcome === 'complete'
-    && run.execution?.runtimeVersion === VERSION && run.execution?.policyHash === expectedPolicy;
+    && isSupportedExecutionProfile(run.execution) && run.execution.policyHash === expectedPolicy;
   const bound = handoff.id === accepted.handoff_run_id && validRun(buildRun, 'build')
     && validRun(checkRun, 'verify') && validRun(reviewRun, 'review') && validRun(handoff, 'handoff')
     && job.source_admission?.status === 'retained' && accepted.head !== accepted.base && candidate.parent === accepted.base
@@ -508,7 +507,7 @@ export class DeliveryService {
     const byID = id => job.runs.find(run => run.id === id);
     const buildRun = byID(accepted.build_run_id), checkRun = byID(accepted.checks_run_id), reviewRun = byID(accepted.review_run_id);
     const validRun = (run, command) => run?.command === command && run.state === 'succeeded' && run.outcome === 'complete'
-      && run.execution?.runtimeVersion === VERSION && run.execution?.policyHash === expectedPolicy;
+      && isSupportedExecutionProfile(run.execution) && run.execution.policyHash === expectedPolicy;
     if (!validRun(buildRun, 'build') || !validRun(checkRun, 'verify') || !validRun(reviewRun, 'review') || !validRun(handoff, 'handoff'))
       throw new QueueError('Build, checks, review and approval do not match the current Factory policy.');
     const phaseEvidence = trustedPhaseEvidence(this.state, job, expectedPolicy,

package/factory/execution-profile.mjs

@@ -6,6 +6,17 @@ import { usageFields } from './usage.mjs';
 import { effectiveInferenceProvider } from './model-environment.mjs';
 import { expectedWebStories, webPolicyHash } from './web-verification.mjs';
 
+// Audited v1 protected evidence writers: 0.8.0 (380f749), 0.9.0 (cdaadef),
+// and this patch. Deliberately independent of VERSION: a release bump is not
+// evidence compatibility. Re-audit this list for every trust-relevant writer,
+// isolation or validation change; remove versions whose guarantees no longer
+// satisfy current policy. See docs/npm.md. This predicate alone grants no trust.
+const SUPPORTED_EXECUTION_RUNTIMES_V1 = new Set(['0.8.0', '0.9.0', '0.9.1']);
+
+export function isSupportedExecutionProfile(profile) {
+  return profile?.version === 1 && SUPPORTED_EXECUTION_RUNTIMES_V1.has(profile.runtimeVersion);
+}
+
 export function withRequestedModel(configuration, requestedModel) {
   const config = structuredClone(configuration);
   if (requestedModel && requestedModel !== config.model) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "software-defence-factory",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "Scoped software delivery and defence investigations with isolated jobs, evidence and review",
   "type": "module",
   "license": "MIT",