@xevy/skills 0.1.69 → 0.1.70

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2,7 +2,7 @@
2
2
  "name": "xevy",
3
3
  "displayName": "Xevy",
4
4
  "description": "Native Xevy SDLC and Features workflows through MCP: plan, implement, review, record QA evidence and publish verified screenshot guides.",
5
- "version": "0.1.69",
5
+ "version": "0.1.70",
6
6
  "author": {
7
7
  "name": "Xevy"
8
8
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xevy/skills",
3
- "version": "0.1.69",
3
+ "version": "0.1.70",
4
4
  "description": "Install Xevy agent skills and secure per-agent MCP transports for Cursor, Claude Code, Codex, and other coding agents.",
5
5
  "type": "module",
6
6
  "keywords": [
@@ -39,6 +39,8 @@ Call `mcp__xevy__list_task_decisions` before implementing. Existing unanswered P
39
39
 
40
40
  ### Worktree protocol
41
41
 
42
+ - In a task Dev Session, reuse the task branch and worktree already registered at startup. Register an additional task through `register_dev_session_branch` only when needed, and edit its returned directory after verified success. Retry a failed registration using the same `branchId`; listing branches or waiting does not complete registration.
43
+
42
44
  - Record the current branch and directory. Derive a canonical branch `xevy/<TASK-ID>-<slug>` using the task code or the first eight characters of its UUID. Reuse an existing task branch; never create a second branch for the same task.
43
45
  - Create or attach a git worktree in a sibling directory and change into it. When resuming, first merge the latest source branch (for example `git merge origin/main`). Do all work in the task worktree.
44
46
  - Verify the absolute worktree path with `git rev-parse --show-toplevel` and its branch with `git branch --show-current` before editing. Keep the task code, UUID, title, absolute worktree path, and branch in the session context. On resume or after changing directories, verify and refresh that context before continuing.
@@ -46,6 +46,20 @@ Review the exact PR and report evidence-based findings. Review remains **read-on
46
46
  - Run relevant tests, lint, type-check, and build checks only where safe in the permitted working directory; avoid commands that rewrite tracked files or require secrets. Select checks from the risk-based matrix, prioritize high-impact paths, and run independent checks concurrently when safe and supported. If not run, explain why. Separate PR-introduced failures from baseline/infrastructure failures where evidence supports it. Never claim there are no code issues solely because CI is green.
47
47
  - Immediately before the verdict, re-read the PR's head and base SHAs. If either changed during review, refresh affected diff, mergeability, checks, and verification or mark the verdict stale/inconclusive; never present an earlier SHA's results as current.
48
48
 
49
+ ### Migration-history safety (when triggered)
50
+
51
+ - **Trigger on behavior, not filenames.** Apply this check when the PR changes migrations, schema, journals or equivalent history metadata, migration configuration, runner code, or startup/deployment migration execution. Include relevant unchanged runner and guard code in the review; a schema or deployment change can alter upgrade safety without adding a migration file.
52
+ - **Establish the actual runner contract from evidence.** Trace the configured entrypoint, resolved runner version/implementation, and startup/deployment wrappers. Identify the authoritative repository journal or equivalent, the database applied-history table/ledger, and the exact eligibility and ordering rules. Distinguish individual migration identity tracking from a latest-timestamp/version watermark; determine strict versus inclusive comparisons, tie handling, checksums/content hashes (including whether they are enforced), dependencies, and reconciliation/startup guards. Cite the relevant code/configuration and source/current-target SHAs; do not impose one framework's rules on another. Filenames and numbering alone never establish eligibility or a defect.
53
+ - **Compare source and current-target histories.** Compare authoritative metadata at the pinned source and current target, using the merge-base to attribute changes. Check lower and equal timestamps/versions, duplicate identities or timestamps, content-hash collisions/mismatches, missing journal entries or migration bodies, dependency gaps/order, and changed or removed already-published identities/content. Inspect relevant concurrently open PRs for competing identities/order when accessible; state that coverage limit when unavailable. Do not infer a conflict solely from similar filenames, or assume that a journal records a checksum the runner actually validates.
54
+ - **Separate branch history from applied database state.** A migration present in the target branch is not proof it was applied to any database. Label applied-state evidence with its environment, provenance and observation time when available; otherwise describe it as a hypothetical upgrade precondition, not a deployment fact. Never infer deployment state from merge order, CI success, or repository metadata alone.
55
+ - **Assess the late-arriving upgrade path.** Evaluate a database where a later migration has already been applied before an incoming earlier migration arrives, including incoming timestamps equal to the applied watermark. Use the runner's actual comparison, identity, dependency and guard rules to determine eligibility and consequences. A clean Git merge or successful fresh installation is not sufficient proof of upgrade safety. Use isolated fixtures/tests (with explicitly disposable state) or a reproducible code trace of the resolved runner and wrappers; never run a migration against a shared, staging, or production database. If isolation cannot be established, use code evidence and state the missing execution proof. Do not claim an isolated test was run when only tracing code.
56
+ - **Distinguish skip, SQL failure, and fail-closed refusal.** Neutral example: an incoming migration has `t_incoming <= t_applied`, while a later migration is already recorded as applied. These are conditional outcomes to investigate, not universal runner behavior:
57
+ - **Silent skipping:** if eligibility requires a timestamp strictly above the watermark, the incoming migration can remain unapplied while the runner reports success. Trace the resulting missing schema/data and affected application flow. **Error if not fixed: No** applies only when evidence establishes no error in that investigated flow; a later failed request is **Yes**, not a harmless skip.
58
+ - **SQL failure:** an individual-identity runner may still attempt the incoming migration, but a missing dependency or incompatible already-upgraded schema can make its SQL fail. Establish the reachable statement/error, transaction or partial-application consequences, and effect on startup/deployment; individual tracking alone does not prove safety. Use **Error if not fixed: Yes** only with demonstrated or code-established failure, otherwise **Unverified**.
59
+ - **Fail-closed refusal:** a reconciliation/startup guard may reject the history before SQL runs. Explain the guard condition, refusal/error, and resulting startup/deployment availability impact. Distinguish intentional protective behavior from a guard defect: a proven refusal of the required upgrade path is a release blocker even when the guard correctly prevents corruption. Never recommend bypassing it. Use **Error if not fixed: Yes** for an established refusal; otherwise **Unverified**.
60
+ - **Apply evidence-based verdicts.** Confirmed unsafe upgrade behavior (silent omission, SQL failure, or refusal preventing the required startup/deployment) is a **Release blocker** and requires **NOT SAFE TO MERGE**; cite the trigger, evidence and concrete unfixed consequence. Missing material runner/history/upgrade evidence requires **MERGE SAFETY UNVERIFIED** unless another established blocker or procedural gate already requires **NOT SAFE TO MERGE**. Put uncertain outcomes in Questions/Risks, not confirmed findings. Numbering differences alone are not a finding. Report which conclusions came from code versus isolated tests and what applied-state evidence remains unverified; a fully verified safe individual-identity upgrade is not a defect merely because its numbering differs.
61
+ - **No live repair or extra mutations.** The review remains read-only for code, records, and merge, with exactly one final PR summary comment by default (unless the user opts out). Do not auto-repair migration history, rewrite journals or applied ledgers, renumber applied migrations, change published identities/checksums, mark migrations applied, or bypass reconciliation/startup guards. Do not migrate shared databases, merge, deploy, or publish packages during review. Describe the smallest safe corrective approach for separately authorized implementation; do not execute it. Fold all migration findings and limitations into the single completed verdict/comment, never a separate mid-review comment.
62
+
49
63
  ## 4. Deliver a verdict
50
64
 
51
65
  - Use plain-text headings and numbered or bulleted lists only; **never use Markdown tables**. Keep the developer-facing response short, actionable, and easy to copy and paste. Do the full review and maintain internal ledgers, but do not print exhaustive inventories or checklists unless requested. Avoid repeating evidence across sections.