@pm_zhousl/xinyun-ai-init 2.0.0 → 3.0.0

package/test-scenarios/v1.13.0-scenarios.md

@@ -1,94 +0,0 @@
-# v1.13.0 Host Adapter and Manual Recovery Scenarios
-
-Scenarios 159-172 are required. Host behavior must use real provider evidence. If the host is unavailable, keep result=not-verified and publishBlocked=true.
-
-## 159. Adapter capability preflight
-Check create, reuse, send, receive, query status, recover, close and control-file access before role sessions.
-
-## 160. Fast block before CodeGraph
-When a required capability is unavailable or unknown, verify blocked status and codeGraphDeferred=true.
-
-## 161. Canonical adapter session ID
-Verify adapter output uses providerSessionId from the supported provider API.
-
-## 162. Ordinary thread ID rejection
-Verify threadId, taskId, filename and history summary cannot bind a role.
-
-## 163. Automatic role session identity
-Verify all five role sessions validate project, role, task, title and cwd.
-
-## 164. Interaction evidence
-Verify send, receive, status query and transcript evidence are required.
-
-## 165. Safe reuse
-Verify old sessions are read and validated before reuse and unverified sessions are not replaced.
-
-## 166. Manual recovery guide
-Verify five Chinese session names, responsibilities, cwd and first read-only prompts are generated.
-
-## 167. Manual binding recovery
-Verify real providerSessionId and evidence restore the original task and role-task IDs.
-
-## 168. Recovery idempotency
-Verify attempt increments and duplicate tasks or sessions are not created.
-
-## 169. Capability permission failure
-Verify permission-denied remains blocked and does not start a large scan.
-
-## 170. Change origin classification
-Verify initialization-created and initialization-updated are distinct from pre-existing-user-change.
-
-## 171. Existing business change isolation
-Verify admin, supplier, uniapp, SQL, configuration and other existing changes are preserved and never rolled back.
-
-## 172. Cross-file recovery consistency
-Verify adapter, preflight, binding, task, assignment, init-result and change report agree on task IDs, attempt, status and evidence.
-
-## 173. Automatic failure decision gate
-Verify automatic role-session failure records `decisionStatus=awaiting-user` and presents exactly `manual-create`, `defer`, and `redetect` without changing to ready.
-
-## 174. Manual creation guide output
-Verify the manual option emits all five standard role names, responsibilities, working directories and first read-only task prompts.
-
-## 175. Confirmed manual binding
-After the explicit user phrase `已创建，继续绑定`, verify canonical provider IDs and identity/interaction evidence are validated before binding.
-
-## 176. Deferred recovery
-Verify `defer` preserves the main task, five role tasks, project snapshot, CodeGraph record and recovery record without duplicate tasks or a repeated scan.
-
-## 177. Host redetection only
-Verify `redetect` runs host preflight only and does not repeat project initialization or broad CodeGraph analysis.
-
-## 178. No implicit choice
-Verify an absent user decision remains blocked, is not auto-skipped and does not trigger repeated prompting.
-
-## 179. Decision record contract
-Verify `userDecision`, `requiredRoleCount`, `createdRoleCount`, `remainingRoleIds`, `decisionStatus`, `decidedAt`, `nextAction` and `decisionEvidence` are mirrored across recovery and init-result.
-
-## 180. Ready gate after recovery
-Verify any missing real role binding or onboarding keeps `projectStatus=blocked` and `executionEligible=false`.
-
-## 181. Recovery idempotency after choice
-Verify each decision resumes the original task IDs and increments `attempt` without creating duplicate tasks or replacing an unverified session.
-
-## Evidence contract for 159-181
-
-Each scenario record must be independently repeatable and contain `scenarioId`, `input`, `expectedOutput`, `actualOutput`, `beforeSnapshotHash`, `afterSnapshotHash`, `changedFiles`, `controlFilesChanged`, `forbiddenOperations`, `evidence`, `sensitiveScan`, `result`, `recordHash`, and `recordedAt`. Cross-file scenarios must compare role-session-binding, provider-session-binding, assignments, the role task, task-index and init-result. `sessionId` and `projectSessionId` must remain null unless the provider canonical `providerSessionId` and all six host operation evidence records are verified.
-
-The current host fixture is `not-verified`; it must not be changed to a passing real-session result without a real canonical provider API response and mutually verifiable interaction log and snapshots.
-
-## 182. Task-first initialization
-
-Verify the main task and five role-execution tasks are created before any provider session operation; all session IDs remain null and the decision status is `awaiting-confirmation`.
-
-## 183. Confirm session creation
-
-After the user selects `create-and-onboard`, verify the provider adapter is entered and no session is bound without canonical ID and six operation evidence.
-
-## 184. Defer session creation
-
-Verify `defer` preserves the task tree and recovery state, keeps the project blocked, and does not rescan or create duplicate tasks.
-
-## 185. Missing session decision
-
-Verify no decision does not auto-create sessions, auto-skip onboarding, or repeat the prompt.