@gobing-ai/spur 0.4.4 → 0.4.5

package/plugins/sp/lib/residual-scan.generated.d.mts

@@ -47,8 +47,6 @@ export declare interface ParsedScanArgs {
     spurBin?: string;
     root: string;
     tmpDir: string;
-    /** The --review-answer <path> flag: the review answer the review-gate mode grades (task 1204). */
-    reviewAnswer?: string;
 }
 export declare const ALLOW_PRAGMA: 'residual-scan:allow';
 export declare function recordedVerdictPath(runDir: string, wbs: string, fs: Pick<typeof import('node:fs'), 'lstatSync' | 'existsSync'>): string;
@@ -70,21 +68,10 @@ export declare function scanResiduals(inputs: ResidualScanInputs): ResidualArtif
 export declare function parseDeferralEntries(raw: unknown): Deferral[];
 export declare function blockingReviewFindings(taskContent: string, deferrals: Deferral[]): ResidualItem[];
 export declare function reviewContractViolations(taskContent: string): Array<{ location: string; text: string }>;
-export declare function reviewConfidenceViolation(
-    reviewAnswer: string,
-    ackLowConfidence: string | undefined,
-): { location: string; text: string } | null;
-export declare function reviewGradingInput(
-    root: string,
-    reviewAnswer: string | undefined,
-    ackLowConfidence: string | undefined,
-    fs: Pick<typeof import('node:fs'), 'readFileSync' | 'statSync'>,
-): { answer: string; ackLowConfidence: string | undefined } | undefined;
 export declare function buildReviewGateArtifact(
     wbs: string,
     taskContent: string,
     deferrals: Deferral[],
-    review?: { answer: string; ackLowConfidence: string | undefined },
 ): { artifact: ResidualArtifact; note: string };
 export declare function parseScanArgs(
     argv: readonly (string | undefined)[],

package/plugins/sp/lib/residual-scan.generated.mjs

@@ -21,14 +21,6 @@ function hasClaimMarker(evidence) {
 function hasCitationForm(evidence) {
   return CITATION_FORMS.some((re) => re.test(evidence));
 }
-var CONFIDENCE_LEVELS = ["HIGH", "MEDIUM", "LOW"];
-function extractAnswerConfidence(text) {
-  const matches = [...text.matchAll(/^\s*Confidence:\s*(\S+)\s*$/gim)];
-  if (matches.length !== 1)
-    return;
-  const value = (matches[0]?.[1] ?? "").toUpperCase();
-  return CONFIDENCE_LEVELS.includes(value) ? value : undefined;
-}
 
 // packages/app/src/services/residual-scan.ts
 var MARKER_PATTERN = /TODO|FIXME|XXX|HACK/;
@@ -202,13 +194,6 @@ function blockingReviewFindings(taskContent, deferrals) {
 }
 function reviewContractViolations(taskContent) {
   const violations = [];
-  const body = reviewBody(taskContent);
-  if (body !== null && extractAnswerConfidence(body.replace(/\*\*/g, "")) === undefined) {
-    violations.push({
-      location: "task-file:Review",
-      text: "Review report carries no single valid `**Confidence:** HIGH | MEDIUM | LOW` line — " + "state the level the report can defend (HIGH: every requirement row MET, every finding " + "dispositioned, evidence cited; MEDIUM/LOW: name the gap)."
-    });
-  }
   for (const row of parseReviewFindings(taskContent)) {
     if (hasClaimMarker(row.text) && !hasCitationForm(row.text)) {
       violations.push({
@@ -219,32 +204,8 @@ function reviewContractViolations(taskContent) {
   }
   return violations;
 }
-function reviewConfidenceViolation(reviewAnswer, ackLowConfidence) {
-  if (ackLowConfidence === "true")
-    return null;
-  const level = extractAnswerConfidence(reviewAnswer.replace(/\*\*/g, ""));
-  if (level === "HIGH" || level === "MEDIUM")
-    return null;
-  return {
-    location: "review-answer:Confidence",
-    text: level === undefined ? "The review answer carries no valid `**Confidence:** HIGH | MEDIUM | LOW` line — a " + "PASS must be graded, or the operator must set ackLowConfidence" : `The review answer graded its PASS ${level} — HIGH/MEDIUM cross unadorned, ` + "LOW/absent needs the operator’s ackLowConfidence"
-  };
-}
-function reviewGradingInput(root, reviewAnswer, ackLowConfidence, fs) {
-  if (reviewAnswer === undefined)
-    return;
-  const path = join(root, reviewAnswer);
-  let isFile = false;
-  try {
-    isFile = fs.statSync(path).isFile();
-  } catch {
-    isFile = false;
-  }
-  return { answer: isFile ? fs.readFileSync(path, "utf8") : "", ackLowConfidence };
-}
-function buildReviewGateArtifact(wbs, taskContent, deferrals, review) {
-  const confidence = review === undefined ? null : reviewConfidenceViolation(review.answer, review.ackLowConfidence);
-  const contractViolations = [...reviewContractViolations(taskContent), ...confidence === null ? [] : [confidence]];
+function buildReviewGateArtifact(wbs, taskContent, deferrals) {
+  const contractViolations = reviewContractViolations(taskContent);
   const items = [
     ...blockingReviewFindings(taskContent, deferrals),
     ...contractViolations.map((v) => ({
@@ -380,7 +341,6 @@ function parseScanArgs(argv, cwd, defaultTmpDir) {
   let spurBin;
   let root = cwd;
   let tmpDir = defaultTmpDir;
-  let reviewAnswer;
   for (let i = 0;i < argv.length; i++) {
     const a = argv[i];
     if (a === undefined)
@@ -391,8 +351,6 @@ function parseScanArgs(argv, cwd, defaultTmpDir) {
       root = argv[++i] ?? root;
     else if (a === "--tmp-dir")
       tmpDir = argv[++i] ?? tmpDir;
-    else if (a === "--review-answer")
-      reviewAnswer = argv[++i];
     else if (a === "--help" || a === "-h")
       return null;
     else if (mode === "")
@@ -400,7 +358,7 @@ function parseScanArgs(argv, cwd, defaultTmpDir) {
     else if (wbs === "")
       wbs = a;
   }
-  return mode === "" || wbs === "" ? null : { mode, wbs, spurBin, root, tmpDir, reviewAnswer };
+  return mode === "" || wbs === "" ? null : { mode, wbs, spurBin, root, tmpDir };
 }
 export {
   ALLOW_PRAGMA,
@@ -419,9 +377,7 @@ export {
   parseScanArgs,
   recordedVerdictPath,
   renderReport,
-  reviewConfidenceViolation,
   reviewContractViolations,
-  reviewGradingInput,
   scanResiduals,
   verdictDisagreementNote
 };

package/plugins/sp/plugin.json

@@ -1,6 +1,6 @@
 {
     "name": "sp",
-    "version": "0.4.4",
+    "version": "0.4.5",
     "description": "Spur — a local-first harness engineering toolkit that wraps mainstream coding agents with constraint checking, workflow orchestration, and history analytics.",
     "extensions": {
         "pi": ["./hooks/pi/guard-extension.ts"]

package/plugins/sp/scripts/residual-scan.mjs

@@ -33,14 +33,6 @@ function hasClaimMarker(evidence) {
 function hasCitationForm(evidence) {
   return CITATION_FORMS.some((re) => re.test(evidence));
 }
-var CONFIDENCE_LEVELS = ["HIGH", "MEDIUM", "LOW"];
-function extractAnswerConfidence(text) {
-  const matches = [...text.matchAll(/^\s*Confidence:\s*(\S+)\s*$/gim)];
-  if (matches.length !== 1)
-    return;
-  const value = (matches[0]?.[1] ?? "").toUpperCase();
-  return CONFIDENCE_LEVELS.includes(value) ? value : undefined;
-}
 var MARKER_PATTERN = /TODO|FIXME|XXX|HACK/;
 var PRIORITY_PATTERN = /^P[1-4]/;
 var RANGE_PRIORITY = /^P[1-4]\s*[\u2013\u2014-]\s*P?[1-4]/;
@@ -212,13 +204,6 @@ function blockingReviewFindings(taskContent, deferrals) {
 }
 function reviewContractViolations(taskContent) {
   const violations = [];
-  const body = reviewBody(taskContent);
-  if (body !== null && extractAnswerConfidence(body.replace(/\*\*/g, "")) === undefined) {
-    violations.push({
-      location: "task-file:Review",
-      text: "Review report carries no single valid `**Confidence:** HIGH | MEDIUM | LOW` line — " + "state the level the report can defend (HIGH: every requirement row MET, every finding " + "dispositioned, evidence cited; MEDIUM/LOW: name the gap)."
-    });
-  }
   for (const row of parseReviewFindings(taskContent)) {
     if (hasClaimMarker(row.text) && !hasCitationForm(row.text)) {
       violations.push({
@@ -229,32 +214,8 @@ function reviewContractViolations(taskContent) {
   }
   return violations;
 }
-function reviewConfidenceViolation(reviewAnswer, ackLowConfidence) {
-  if (ackLowConfidence === "true")
-    return null;
-  const level = extractAnswerConfidence(reviewAnswer.replace(/\*\*/g, ""));
-  if (level === "HIGH" || level === "MEDIUM")
-    return null;
-  return {
-    location: "review-answer:Confidence",
-    text: level === undefined ? "The review answer carries no valid `**Confidence:** HIGH | MEDIUM | LOW` line — a " + "PASS must be graded, or the operator must set ackLowConfidence" : `The review answer graded its PASS ${level} — HIGH/MEDIUM cross unadorned, ` + "LOW/absent needs the operator’s ackLowConfidence"
-  };
-}
-function reviewGradingInput(root, reviewAnswer, ackLowConfidence, fs) {
-  if (reviewAnswer === undefined)
-    return;
-  const path = join(root, reviewAnswer);
-  let isFile = false;
-  try {
-    isFile = fs.statSync(path).isFile();
-  } catch {
-    isFile = false;
-  }
-  return { answer: isFile ? fs.readFileSync(path, "utf8") : "", ackLowConfidence };
-}
-function buildReviewGateArtifact(wbs, taskContent, deferrals, review) {
-  const confidence = review === undefined ? null : reviewConfidenceViolation(review.answer, review.ackLowConfidence);
-  const contractViolations = [...reviewContractViolations(taskContent), ...confidence === null ? [] : [confidence]];
+function buildReviewGateArtifact(wbs, taskContent, deferrals) {
+  const contractViolations = reviewContractViolations(taskContent);
   const items = [
     ...blockingReviewFindings(taskContent, deferrals),
     ...contractViolations.map((v) => ({
@@ -390,7 +351,6 @@ function parseScanArgs(argv, cwd, defaultTmpDir) {
   let spurBin;
   let root = cwd;
   let tmpDir = defaultTmpDir;
-  let reviewAnswer;
   for (let i = 0;i < argv.length; i++) {
     const a = argv[i];
     if (a === undefined)
@@ -401,8 +361,6 @@ function parseScanArgs(argv, cwd, defaultTmpDir) {
       root = argv[++i] ?? root;
     else if (a === "--tmp-dir")
       tmpDir = argv[++i] ?? tmpDir;
-    else if (a === "--review-answer")
-      reviewAnswer = argv[++i];
     else if (a === "--help" || a === "-h")
       return null;
     else if (mode === "")
@@ -410,7 +368,7 @@ function parseScanArgs(argv, cwd, defaultTmpDir) {
     else if (wbs === "")
       wbs = a;
   }
-  return mode === "" || wbs === "" ? null : { mode, wbs, spurBin, root, tmpDir, reviewAnswer };
+  return mode === "" || wbs === "" ? null : { mode, wbs, spurBin, root, tmpDir };
 }
 
 // plugins/sp/lib/spur-bin.ts
@@ -420,7 +378,7 @@ function spurCommand(spurBin) {
 }
 
 // plugins/sp/scripts/residual-scan.ts
-var RESIDUAL_SCAN_USAGE = "usage: residual-scan.ts <scan|fold|settle|report|review-gate> <wbs> [--spur-bin <bin>] [--root <dir>] [--tmp-dir <dir>] [--review-answer <path>]";
+var RESIDUAL_SCAN_USAGE = "usage: residual-scan.ts <scan|fold|settle|report|review-gate> <wbs> [--spur-bin <bin>] [--root <dir>] [--tmp-dir <dir>]";
 function run(cmd, args, cwd) {
   const result = spawnSync(cmd, args, { cwd, encoding: "utf8" });
   if (result.error !== undefined)
@@ -515,8 +473,7 @@ function reviewGateMode(opts, env, io) {
   const runDir = join2(opts.root, ".spur", "run");
   fs.mkdirSync(runDir, { recursive: true });
   const { content } = loadTask(env, opts.spurBin, opts.wbs, opts.root);
-  const grading = reviewGradingInput(opts.root, opts.reviewAnswer, env.ackLowConfidence, fs);
-  const gate = buildReviewGateArtifact(opts.wbs, content, readDeferrals(runDir, opts.wbs), grading);
+  const gate = buildReviewGateArtifact(opts.wbs, content, readDeferrals(runDir, opts.wbs));
   fs.writeFileSync(join2(runDir, `${opts.wbs}-residuals.json`), `${JSON.stringify(gate.artifact, null, 2)}
 `);
   io.out(gate.note);
@@ -671,9 +628,7 @@ export {
   parseScanArgs,
   recordedVerdictPath,
   renderReport,
-  reviewConfidenceViolation,
   reviewContractViolations,
-  reviewGradingInput,
   scanResiduals2 as scanResiduals,
   verdictDisagreementNote
 };

package/plugins/sp/scripts/residual-scan.ts

@@ -10,7 +10,7 @@ import { spurCommand } from '../lib/spur-bin';
 
 export * from '../lib/residual-scan.generated.mjs';
 export const RESIDUAL_SCAN_USAGE =
-    'usage: residual-scan.ts <scan|fold|settle|report|review-gate> <wbs> [--spur-bin <bin>] [--root <dir>] [--tmp-dir <dir>] [--review-answer <path>]';
+    'usage: residual-scan.ts <scan|fold|settle|report|review-gate> <wbs> [--spur-bin <bin>] [--root <dir>] [--tmp-dir <dir>]';
 export type ScanEnv = { spurBin?: string } & Record<string, string | undefined>;
 export type ScanIo = { out: (line: string) => void; err: (line: string) => void };
 export type ScanOptions = { cwd?: string; io?: ScanIo };
@@ -106,16 +106,14 @@ function scanMode(opts: ParsedArgs, env: ScanEnv, io: ScanIo): number {
 /**
  * Task 1122 R2: the review-time gate — the record sweep's review-finding slice
  * (core.buildReviewGateArtifact) at the review PASS edges; writes the same `<wbs>-residuals.json`
- * the test-fix hop reads. Exit 1 on an open P1-P3 finding, or on a review answer graded LOW or left
- * ungraded without `env.ackLowConfidence` (task 1204, graded via `core.reviewGradingInput` — it
- * cannot sit inline in the edge because ADR-115 caps a guard at 5 logical commands).
+ * the test-fix hop reads. Exit 1 on an open P1-P3 finding. The answer-grade rule (1204) was
+ * retired with the asserted confidence machinery (F511); findings stay the gate.
  */
 function reviewGateMode(opts: ParsedArgs, env: ScanEnv, io: ScanIo): number {
     const runDir = join(opts.root, '.spur', 'run');
     fs.mkdirSync(runDir, { recursive: true });
     const { content } = loadTask(env, opts.spurBin, opts.wbs, opts.root);
-    const grading = core.reviewGradingInput(opts.root, opts.reviewAnswer, env.ackLowConfidence, fs);
-    const gate = core.buildReviewGateArtifact(opts.wbs, content, readDeferrals(runDir, opts.wbs), grading);
+    const gate = core.buildReviewGateArtifact(opts.wbs, content, readDeferrals(runDir, opts.wbs));
     fs.writeFileSync(join(runDir, `${opts.wbs}-residuals.json`), `${JSON.stringify(gate.artifact, null, 2)}\n`);
     io.out(gate.note);
     return gate.artifact.counts.blocking > 0 ? 1 : 0;

package/plugins/sp/skills/code-verification/SKILL.md

@@ -341,7 +341,6 @@ Verdict: PASS    (or PARTIAL / FAIL)
 
 ```markdown
 Verdict: PASS
-Confidence: HIGH
 
 ### Per-Requirement Traceability
 | Req | Status | Evidence |
@@ -360,7 +359,7 @@ Confidence: HIGH
 ```
 
 The per-requirement traceability table MUST use `| Req | Status | Evidence |` (exactly this header, no `R#`/`R`/`Requirement` variant — `Status` in column 2 — and no extra columns between Req and Status). The Acceptance Criteria table MUST use `| AC | Status | Evidence Type | Evidence |`.
-The answer MUST carry exactly one `Confidence: HIGH|MEDIUM|LOW` line (task 1068): the verifier's stated confidence in the verdict — HIGH = fresh executable evidence + re-read anchors this run; MEDIUM = partial reliance on prior evidence, external/delegated outcomes, or an unstable tree; LOW = key evidence not re-executed. A missing or out-of-vocabulary line fails lint (`confidence-missing` / `confidence-value`) and blocks derivation; the value lands in the verdict artifact's `confidence` field and the recorded `## Testing` section.
+The answer carries no `Confidence:` line (F511, task 1207): model-asserted confidence is not verification — a verifier that can write a PASS can write `HIGH`. What the old level compressed now lives in the evidence cells themselves: cite fresh executable evidence and name residual gaps explicitly. Legacy answers that still carry a confidence line parse (the value is ignored); no lint code reads it and the artifact and recorded `## Testing` section carry no confidence value.
 The answer MUST cite a source for external API/library claims in Requirement/AC evidence cells: a cell asserting a scoped-package (`@scope/name`), `node_modules/`, semver-version (`x.y.z`), or backticked function-call (`` `name(args)` ``) claim is rejected with `evidence-citation` unless the SAME cell carries a citation — a repo `path:line(-end)` (backticked or bare), the external named-origin form (@origin `path` line N), or a URL. Cross-cell references ("receipt above") do not count; marker-free receipts ("bun test 398 pass / 0 fail") need no citation.
 **MUST NOT:** place a `Severity` column between `Req` and `Status`. The parser tolerates variants
 as defense-in-depth; this contract is canonical.

package/plugins/sp/skills/code-verification/references/verdict-schema.md

@@ -35,42 +35,21 @@ interface VerifyVerdict {
     status: 'pass' | 'fail' | 'warn';
     evidence: string;
   }>;
-  /** Verifier confidence (task 1068 R3). REQUIRED for PASS — the done gate denies
-   *  a confidence-less PASS. Accepted case-insensitively, normalized to uppercase. */
-  confidence?: 'HIGH' | 'MEDIUM' | 'LOW';
+  // F511 (task 1207): no asserted `confidence` field. Legacy artifacts that still carry one
+  // parse with the value ignored — unknown legacy keys are tolerated on read.
 }
 ```
 
-## Confidence level (task 1068 R3)
+## No asserted confidence (F511, task 1207)
 
-A PASS verdict must state the verifier's confidence: `"confidence": "HIGH" | "MEDIUM" | "LOW"`.
-The value is case-insensitive on read (normalized to uppercase), but a present value outside the
-enum invalidates the artifact, and a PASS with the field absent is denied at the `* → done`
-transition with a remediation naming the field (`--force-done` remains the documented escape).
-The verify answer's `Confidence:` lint rule (producer side) already guarantees the field for
-pipeline-produced artifacts; this closes the hand-authored / pre-1068 artifact hole.
-
-### Coherence: the level must be earned (task 1133)
-
-Presence and vocabulary are not enough — the level has to match the rows in the same answer, so the
-lint rejects a level that contradicts its own evidence. Two rejection classes, both addressed to the
-`Confidence:` line and both capped by the shared `ANSWER_LINT_MAX_FINDINGS` budget:
-
-- `confidence-unwarranted` — `HIGH` while any requirement row normalizes to `PARTIAL`/`UNMET`, any
-  acceptance-criteria row does not normalize to `MET`, or any `MET` row's evidence is hedged.
-  A `HIGH` claim says the evidence needs no re-check; a non-MET or hedged row says the opposite.
-- `confidence-understated` — `LOW` while at least one requirement row exists and every requirement
-  and acceptance-criteria row normalizes to `MET`. The evidence already did the work, so `LOW`
-  misreports the state as unproven.
-
-`MEDIUM` carries no coherence rule in either direction: it is the level a verifier uses for a caveat
-with no row to point at, and closing it would force either an overclaimed `HIGH` or an unusable
-`LOW`. The level is normalized to uppercase before the decision, so `high` is judged as `HIGH`.
-
-Set the level from the rows, not the mood: all rows `MET` with fresh evidence is `HIGH`; a
-`PARTIAL`/`UNMET` row or a hedge means `MEDIUM`, not `HIGH`. An unwarranted level does not merely
-warn — the lint rejects the answer and no verdict artifact is written, so the level is worth
-choosing deliberately before the verdict line is finalized.
+Verdict artifacts carry no `confidence` field and verify answers no `Confidence:` line. The
+1068/1133 machinery that required, linted and coherence-checked a model-asserted
+`HIGH | MEDIUM | LOW` was retired: a verifier that can write a PASS can write `HIGH`, so the grade
+verifies nothing. What the level compressed belongs in the evidence cells — cite fresh executable
+evidence and name residual gaps explicitly. The done gate no longer denies a confidence-less PASS:
+it checks the proof digests, which are the part a hand-edited artifact cannot fake. The DERIVED
+confidence family is a different thing and stays: feature-verification receipts (ADR-131, 1196),
+the decision subsystem threshold, history-anatomy reading.
 
 ## Compatibility alias: `scenario` row key
 

package/plugins/sp/skills/spur-dev/references/execution-workflow.md

@@ -171,17 +171,13 @@ Two branches reach the bounded repair hop, not one (session finding after 1088):
   an on-graph, bounded path to remediation instead of dead-ending the run, and the fix re-enters
   quality → review → verify on a freshly captured proof digest.
 
-The completion gate also reads the verifier's confidence (session finding after 1088): the verify
-answer's `Confidence: HIGH|MEDIUM|LOW` line reaches the verdict artifact, and both `verify → record`
-and `record → done` refuse a `LOW` (or absent) level unless the run was launched with
-`--vars '{"ackLowConfidence":"true"}'`. A PASS the verifier would not stand behind is an operator
-risk decision, so it takes an operator acknowledgement — not a silent certification.
-The CLI-layer done gate (`done-transition-guard`, task 1068 R3) separately requires the artifact to *state* a
-level at all: a PASS artifact whose `confidence` is missing is denied there too, and a present but
-out-of-vocabulary value fails the read closed (`invalid confidence field`), so a hand-driven
-`task update <wbs> done` — which is how this pipeline itself reaches `done` (`--no-lifecycle`) —
-cannot certify a verdict that carries no confidence. `LOW` is accepted at that gate; the
-acknowledgement rule above stays the pipeline's.
+The completion gate reads deterministic evidence only (F511, task 1207): both `verify → record` and
+`record → done` check the proof digests in `.spur/run/<wbs>-verdict.json` — verdict PASS, matching
+run/definition digests, review stage completed. No confidence is read, stated or acknowledged; the
+asserted `Confidence:` line and the `ackLowConfidence` operator var were retired because a model
+that can write a PASS can write `HIGH` — the grade verified nothing. What protects a hand-driven
+`task update <wbs> done` is unchanged: the digests must match the run's captured proof, and the
+review stage must actually be completed in the artifact.
 
 Agentic steps use the pure slash inputs declared by each YAML `agent.run` action (ADR-043). The
 workflow engine dispatches them; the interactive driver invokes their backing skills in-session.

package/plugins/sp/skills/spur-dev/references/inline-pipeline-driver.md

@@ -844,9 +844,10 @@ leave no `.spur/run/<wbs>-check-receipt.json`. The deciding artifacts are then
 1. **Drive the pipeline** for anything that must be certified: only a digest-bound full receipt
    satisfies a review/verify/record boundary (`sp-spur-check`), and the `test` hop owns the capture.
 2. **When a host-driven pass is unavoidable, say so in the verdict** — name the status file and gate
-   log as the evidence and grade confidence `MEDIUM`. A `HIGH` claim needs re-runnable evidence from a
-   checked path (the `sp-code-verification` ladder); claiming a receipt that was never written is the
-   failure mode this note exists to prevent (observed across four A91 tasks, 2026-10-12).
+   log as the evidence, and mark the reliance explicitly in the evidence cell (a host-driven gate is
+   not re-runnable proof from a checked path; the `sp-code-verification` ladder is). Claiming a
+   receipt that was never written is the failure mode this note exists to prevent (observed across
+   four A91 tasks, 2026-10-12).
 
 **A mismatch names the drifted paths (R5).** At gate entry the pipeline snapshots the non-corpus tree
 state (`git status --porcelain=v1 -uall` plus `git diff --name-only HEAD`, excluding
@@ -977,14 +978,14 @@ Each item below cost a driver cycle to discover. They are contracts, not tips.
   `.spur/run/<wbs>-diffstat.json` and never on command output. Never the bare unguarded
   source-repo path form — the script-contract check forbids it on a shipped surface because it
   shadows the installed twin in a consumer.
-- **The verify answer grammar is exact.** One `Verdict:` line, one `Confidence:` line, then
+- **The verify answer grammar is exact.** One `Verdict:` line, then
   `### Per-Requirement Traceability` (`| Req | Status | Evidence |`) and
   `### Acceptance Criteria Verification` (`| AC | Status | Evidence Type | Evidence |`). Requirement
   statuses are `MET | PARTIAL | UNMET`; AC statuses add `N/A`; every AC row id must match a declared
   scenario title verbatim, including its `(req: ...)` suffix. A `MET` row whose evidence hedges
   (`likely`, `probably`, `seems`, `appears`, `possibly`, `presumably`) is rejected as
-  `evidence-hedged`, and a level the rows do not earn is rejected as `confidence-unwarranted` or
-  `confidence-understated`. `spur task verdict` lints before writing, so a rejected answer leaves no
+  `evidence-hedged`. No `Confidence:` line exists (F511, task 1207) — legacy answers that carry one
+  parse with the value ignored. `spur task verdict` lints before writing, so a rejected answer leaves no
   artifact and exits non-zero.
 - **Harness tooling refuses direct task-file writes.** Resolve a merge conflict in a task file by
   choosing a git side, then applying the corpus delta through `spur task update` (for example