v1.91.7.0 feat: add functional QA and pre-publication docs checks (#2983)

* feat: add surface-aware exploratory QA and ship documentation gates

* test: preserve delegated QA setup authority after main integration

* fix(qa): clarify exploration order and preserve report artifacts

* test(qa): follow the shared setup reference directly

* refactor(ship): make verification and recovery routes explicit

* test(ship): align evidence and review guards with explicit routes

* fix(workflows): clarify ship recovery and functional QA evidence

* fix(workflows): clarify approval recovery and full QA coverage

* refactor(workflows): order review transactions and clarify ship state

* fix(ship): clarify final verification and fail closed at publication

* fix(evals): attribute native atomic documentation writes

* fix(ship): clarify recovery and documentation lifecycle guidance

* fix(test): preserve observed native placeholder styling in CI

* fix(codex): report watchdog timeouts without a process-exit race

* Checkpoint functional QA implementation and workflow validation repairs

* Fix documentation and shared-review fixture contracts

* docs: clarify judge reuse and evaluation supervision

* test: align review evidence and selected case contracts

* test: verify append-only documentation checkpoints and recovery

* fix: qualify QA workflows and CI validation repairs

* fix: launch shared-libs fixture scripts on Windows

* fix: qualify QA deadlines, fixture isolation, and shard cleanup

* fix: preserve qualified QA and cancellation repairs

* fix: enforce functional fixture authority and share strict event decoding

* fix: retain free-test evidence and explain recovery

* fix: reject malformed native evidence after decoder consolidation

* test: use reliable capture for telemetry privacy filters

* test: refresh measured quick coverage and document validation costs

* Fix native fixture receipts and preserve VM validation evidence

* Align negative judge controls with upstream clarity policy

* Fix report-only QA preparation and public evidence handling

* Clarify QA-only preparation and current-report preservation

* Stream Ship quality judgments with an explicit 64k response contract

* Validate compact judge reasoning locally with supported wire schema

* Align functional QA fixture instructions with evidence acceptance

* Bind native browser diagnostics to execution evidence and align review verdicts

* Preserve native diagnostic line boundaries

* Serialize functional QA evidence from native captures

* Keep large QA evidence fixture payload out of Windows argv

scripts/resolvers/learnings.ts

@@ -34,6 +34,20 @@ export function generateLearningsSearch(ctx: TemplateContext, args?: string[]):
     );
   }
   const queryFlag = queryArg ? ` --query "${queryArg}"` : '';
+  const findingKind = ctx.skillName === 'qa' || ctx.skillName === 'qa-only' ? 'QA' : 'review';
+
+  if (ctx.skillName === 'qa-only') {
+    return `## Prior Learnings
+
+Read this project's existing learnings.jsonl only if its directory is already known
+and the caller permits that Read. Otherwise skip this optional lookup.
+${queryArg ? `Look for notes matching "${queryArg}".\n` : ''}Do not run gstack-learnings-search here: its slug helper can update a cache.
+Do not change configuration, enable cross-project search or create a learning store.
+
+Treat old notes as leads, not proof. When a QA finding matches a past learning,
+cite it as "Prior learning applied: [key] (confidence N/10, from [date])" and verify
+the current behavior. Reading old notes never requires writing new ones.`;
+  }
 
   if (getHostConfig(ctx.host).learningsMode === 'basic') {
     // Basic learnings mode (host config learningsMode: 'basic' — every host
@@ -47,7 +61,7 @@ Search for relevant learnings from previous sessions on this project:
 $GSTACK_BIN/gstack-learnings-search --limit 10${queryFlag} 2>/dev/null || true
 \`\`\`
 
-If learnings are found, incorporate them into your analysis. When a review finding
+If learnings are found, incorporate them into your analysis. When a ${findingKind} finding
 matches a past learning, note it: "Prior learning applied: [key] (confidence N, from [date])"`;
   }
 
@@ -81,7 +95,7 @@ If B: run \`${ctx.paths.binDir}/gstack-config set cross_project_learnings false\
 
 Then re-run the search with the appropriate flag.
 
-If learnings are found, incorporate them into your analysis. When a review finding
+If learnings are found, incorporate them into your analysis. When a ${findingKind} finding
 matches a past learning, display:
 
 **"Prior learning applied: [key] (confidence N/10, from [date])"**