@1aboveio/skills 1.0.7 → 1.0.8

package/skills/engineering/resolve-issues/references/implementation.md

@@ -59,6 +59,12 @@ boundary, workspace, outcome, validation, and return contract; prescribe no
 method or evidence format. Name a leaf skill only as the findings record it
 (`proof.suite.skill`, with `local`).
 
+A continuation inherits the immediate acceptance checkpoint and history from
+[Delivery progress](../SKILL.md#delivery-progress). In its existing result, state what
+new evidence changes the next action; if nothing changed, say so instead of relaunching
+the same work. A passing setup check is not a substitute for the blocked behavior.
+No additional report or result schema is required.
+
 Have the implementer treat findings as leads, find its own code, and report
 any `product`, `scope`, `design`, or `approval` question the explorer missed and any
 human-only proof. Report each question in the result's `decisionNeeded`
@@ -87,7 +93,9 @@ implementer in its kept workspace with the brief and its findings entry.
    options, recommendation; options are ways to proceed, and staying
    blocked is never one). Fix workers write the same file. Return
    nothing else: no artifact hashes, version inventories, screenshots,
-   copied logs, or earlier attempts.
+   copied logs, or earlier attempts. For a continuation, include the current checkpoint,
+   outcome and relevant prior-result links in the existing integration notes; do not
+   duplicate the full attempt history.
 
 After 2 fix cycles without progress, or a stuck or late worker, follow
 [expire.md](expire.md). Start the next worker in the same workspace with the

package/skills/engineering/resolve-issues/references/task-plan.md

@@ -85,7 +85,7 @@ Fleet `status`: `pending`, `in-flight`, `succeeded`, `failed`,
 | `workerKind` | `implement`, `fix`, or `review`, set with `worker`; the [live-capacity scheduler](implementation.md#live-capacity) (`next-actions.mjs`) prints `worker-kind` for any other kind or none. An infrastructure diagnosis or a test-first worker is a `fix` worker. The explorer is the `explore` fleet row's worker, never a unit's; a merge-queue watcher is not a worker |
 | `estimatedLines` | Explorer estimate |
 | `sizeCheck` | Measures, `verdict` (the size check's per-unit verdict; `stop` means held), scope and proof verdicts, split or verification path; `runWhole: true` once a recommendation to run a held unit whole is accepted |
-| `note` | SHA, expiry reason code, failure and the response taken, or blocker |
+| `note` | SHA, expiry reason code, failure and response, or blocker; for active debugging, the immediate acceptance checkpoint, baseline/result link and next distinguishing test ([delivery progress](../SKILL.md#delivery-progress)) |
 | `pr`, `headSha`, `reviewedHead` | PR URL, current HEAD (recorded from the implementer's first pushed commit on, so the draft PR opens early), last HEAD whose verdict was `pass` (reviewed or carried) |
 | `delivery` | `building`, `opening`, `review`, `ci`, `merged`, `blocked` |
 | `reviewRound`, `fixRound` | Review-attempt/file number, and the count of blocking-fix cycles (a record, not a cap); record both from the review/verdict, never charge skips, or reviews that follow a passing one, as fixes |
@@ -259,6 +259,9 @@ changes, unit outcomes, validation turning red or green, canary events,
 retries and escalations, newly runnable dependencies, PR open, HEAD change, or
 merge, and about every 5 minutes; skip when nothing changed.
 
-Final board: each unit's outcome with its scope and proof verdicts, every PR URL, SHA,
-and merge state, retry and escalation totals, each blocker, and the exploration
-path.
+Final board: lead with behavior delivered and criteria still unproved, then each unit's
+scope and proof verdicts, PR URL, SHA, merge state, retries, blocker and exploration path.
+Use existing result timestamps and CI records, when available, for time to reproduction,
+time to verified correction and full CI runs per delivered change. Mark missing data as
+unknown. Worker/test counts describe activity, not acceptance; do not add a reporting
+pipeline or duplicate the plan to produce these summaries.

package/skills/engineering/resolve-release/SKILL.md

@@ -4,7 +4,7 @@ description: "Slash/explicit-only (/resolve-release). Full GitHub Flow release f
 disable-model-invocation: true
 metadata:
   workflow-role: coordinator
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Resolve release

package/skills/engineering/rush-issues/SKILL.md

@@ -6,7 +6,7 @@ metadata:
   workflow-role: coordinator
 dependencies:
   - resolve-issues
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Rush issues (shortcut of resolve-issues)
@@ -50,7 +50,10 @@ question.
      and complete the goal
      ([done.md](../resolve-issues/references/done.md#close-the-run)).
 3. Everything else — run rules, stages, scripts, review, CI and merge, and the
-   done criteria — applies exactly as `resolve-issues` states it.
+   done criteria — applies exactly as `resolve-issues` states it. In particular,
+   [Delivery progress](../resolve-issues/SKILL.md#delivery-progress) applies in shortcut
+   mode too: keep one immediate checkpoint per active unit, justify infrastructure and
+   reassess repeated non-convergence. More worker activity is not a reason to reset it.
    The shared [task-plan checkpoints](../resolve-issues/references/task-plan.md#checkpoints)
    apply too: on Pi, bind or reload through `update_plan` with the absolute
    workflow path and persisted revision (no event means read-only), then

package/skills/engineering/rush-release/SKILL.md

@@ -6,7 +6,7 @@ metadata:
   workflow-role: coordinator
 dependencies:
   - resolve-release
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Rush release (shortcut of resolve-release)

package/skills/engineering/test-quality/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: test-quality
 description: "Seven principles for tests that catch real bugs, and an audit that reports weak, redundant, and not-coverage tests without fixing them. Use when writing, changing, or reviewing tests, or when asked whether tests are useful, redundant, over-mocked, flaky, only assert static text, or test config files, or asked to make a slow test suite faster without losing coverage, or when the user asks to write the testing conventions into a repo's CONTRIBUTING.md. NOT defining what a spec must prove (ensure-coverage) or authoring browser tests (e2e-test)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Test Quality

package/skills/risk-compliance/compliance-audit/SKILL.md

@@ -2,7 +2,7 @@
 name: compliance-audit
 version: 2.9.0
 description: "Audit operations against financial-compliance checklists (AML/KYC, VARS, PCI-DSS, TPA oversight, onboarding, transaction monitoring). Produces tracker.md (with a tracker.xlsx export) and phase-trail.md with layered validation; cites evidence by original filename. Input: reg-parser or the built-in VARS checklist."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Compliance Audit

package/skills/risk-compliance/contract-compare/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: contract-compare
 description: "Compare two or more contracts side-by-side for structured diff, gap analysis, and benchmarking. Use when: comparing contracts or agreements, contract diff, compare terms, vendor-vs-vendor, compare our template vs theirs, compliance gap between contracts. NOT for single-contract risk review — use contract-review for that."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Contract Compare

package/skills/risk-compliance/contract-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: contract-review
 description: "Review contracts for legal, commercial, and compliance risks via convert → chunk review → merge → validate (+ optional mandate preprocessing). Use for reviewing, auditing, or checking any contract, agreement, NDA, MSA, or SLA; input a file path (PDF/DOCX/TXT) or pasted text."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Contract Review

package/skills/risk-compliance/doc-authenticity/SKILL.md

@@ -3,7 +3,7 @@ name: doc-authenticity
 version: 0.4.1
 description: "Screen PDF documents and raster images for fabrication, tampering, Photoshop or other image-editor use, and content validity. Detects file type, runs format-specific authenticity forensics, classifies bank statements, conversation logs, invoices, agreements, and other documents, then applies type-specific validity checks. Produces separate authenticity (NO_EVIDENCE_OF_MODIFICATION / SUSPICIOUS / LIKELY_MODIFIED / INCONCLUSIVE) and validity (VALID / INVALID / INCONCLUSIVE) verdicts. Use whenever a user asks whether a document, screenshot, scan, statement, invoice, contract, chat log, receipt, or payment evidence is genuine, original, edited, Photoshopped, manipulated, fake, or valid."
 disable-model-invocation: true
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Document and Image Authenticity

package/skills/risk-compliance/fraud-analysis/SKILL.md

@@ -10,7 +10,7 @@ description: >
   impact, and a business report. Use for fraud, scam, mule, account-takeover,
   chargeback, dispute, transfer, collection, or payout risk analysis even when the
   user does not name this skill.
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Fraud Analysis

package/skills/risk-compliance/payment-analysis/SKILL.md

@@ -14,7 +14,7 @@ description: >
   transactions" — even if they do not say payment-analysis. Do NOT use for
   supervised fraud-rule mining (fraud-analysis) or TLD / MCC-miscoding
   clusters (tld-detection).
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Payment Analysis

package/skills/risk-compliance/similar-domain/SKILL.md

@@ -8,7 +8,7 @@ description: >
   links, an entity chain, and a watchlist for the operator's next domains.
   Not transaction data (tld-detection) or fraud rules (fraud-analysis).
 disable-model-invocation: true
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Similar Domain

package/skills/risk-compliance/tld-detection/SKILL.md

@@ -11,7 +11,7 @@ description: >
   with a ≤3-sentence summary.
   Not payment-analysis, fraud-analysis, or website research (similar-domain).
 disable-model-invocation: true
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # TLD Detection