@1aboveio/skills 1.0.15 → 1.0.17

package/skills/engineering/resolve-issues/scripts/size-check.mjs

@@ -30,7 +30,8 @@
 // (ok, warn, hold, stop, or exploration-unfinished); 2 for a bad plan or command.
 // `exploration-unfinished` (printed as `{ verdict, reason }`) means findings that are unreadable,
 // not version 2, or missing a planned unit, its `slice`, its `proof`, or its `estimatedLines`;
-// only the explorer fixes it. --exit-verdict restores the old exit codes for one release
+// complete the preflight findings using exploration.md's owner routing.
+// --exit-verdict restores the old exit codes for one release
 // (deprecated): 0 for ok/warn, 4 for hold, 1 for stop, 3 for exploration-unfinished.
 
 import { readFileSync } from 'node:fs'
@@ -78,7 +79,7 @@ export const FINDINGS_VERSION = 2
 
 export class SizeCheckError extends Error {}
 
-// Unfinished exploration: the explorer, not the orchestrator, fixes it.
+// Unfinished assessment; keep the exported error and verdict compatible with saved runs.
 export class ExplorationUnfinished extends SizeCheckError {}
 
 function unitsOf(plan) {
@@ -262,9 +263,9 @@ function environmentChecks(units, byUnit) {
 // ---- The whole check ----
 
 // A unit counts as explored once its entry carries a valid `slice`, `proof`,
-// and `estimatedLines`; the explorer's scaffold (an empty entry per unit) does not pass.
+// and `estimatedLines`; a scaffold (an empty entry per unit) does not pass.
 function findingsUnitsOf(findings, units) {
-  const unfinished = (why) => new ExplorationUnfinished(`exploration unfinished: ${why}; continue the explorer`)
+  const unfinished = (why) => new ExplorationUnfinished(`exploration unfinished: ${why}; complete the preflight findings`)
   if (findings?.version !== FINDINGS_VERSION) throw unfinished(`findings version is ${JSON.stringify(findings?.version)}, expected ${FINDINGS_VERSION}`)
   const byUnit = findings.units
   if (!byUnit || typeof byUnit !== 'object' || Array.isArray(byUnit)) throw unfinished('findings has no units map')
@@ -481,7 +482,7 @@ if (isMainModule(import.meta.url)) {
     process.exitCode = opts.exitVerdict ? EXIT[result.verdict] : 0
   } catch (error) {
     if (error instanceof ExplorationUnfinished) {
-      // Unfinished exploration is an answer (the explorer continues), not a failure of the script.
+      // Incomplete findings are an answer, not a failure of the script.
       process.stdout.write(`${JSON.stringify({ verdict: 'exploration-unfinished', reason: error.message }, null, 2)}\n`)
       process.exitCode = process.argv.includes('--exit-verdict') ? 3 : 0
     } else {

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.47.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Resolve release

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

@@ -1,12 +1,12 @@
 ---
 name: rush-issues
-description: "Slash/explicit-only (/rush-issues). No-questions shortcut of /resolve-issues: drive an issue, epic, or feature spec to reviewed, green PRs, one per issue, and merge each (through the queue when there is one). Takes every preflight default (recommended implementer unless the invocation pins one, the default branch, autonomous merge with blocker fixes, full scheduler mode unless scheduler= says otherwise, the drafted plan) and asks nothing, even at preflight; invoking it is the authorization. Like resolve-issues, never blocks on the human: it takes the automatic answer (the recommendation, formed if none; filed splits) and defers what only a human can do (a looser required check, shared-environment changes, missing access) on its owning issue while the rest ships. Posts the dropbox, then completes the goal. Do not auto-select. NOT for choosing the implementer, target branch, supervised merge, or trimming a plan or moving units to later (resolve-issues), and NOT for release work (rush-release)."
+description: "Slash/explicit-only (/rush-issues). No-questions shortcut of /resolve-issues: drive an issue, epic, or feature spec to reviewed, green PRs, one per issue, and merge each (through the queue when there is one). Takes every preflight default (the catalog's implementer slot unless the invocation pins one, the default branch, autonomous merge with blocker fixes, full scheduler mode unless scheduler= says otherwise, the drafted plan) and asks nothing, even at preflight; invoking it is the authorization. Like resolve-issues, never blocks on the human: it takes the automatic answer (the recommendation, formed if none; filed splits) and defers what only a human can do (a looser required check, shared-environment changes, missing access) on its owning issue while the rest ships. Posts the dropbox, then completes the goal. Do not auto-select. NOT for choosing the target branch, supervised merge, or trimming a plan or moving units to later (resolve-issues), and NOT for release work (rush-release)."
 disable-model-invocation: true
 metadata:
   workflow-role: coordinator
 dependencies:
   - resolve-issues
-release-version: 0.47.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Rush issues (shortcut of resolve-issues)
@@ -21,8 +21,8 @@ CI.** Make the decisions that get there. `resolve-issues`'
 are guidelines, and every rule serves the goal rather than restricting you.
 
 `/rush-issues` runs the `resolve-issues` workflow in **shortcut mode**: the
-recommended implementer (or the one `implementer=<id[@effort]>` pins; the run
-stops if it is unavailable, never swapping in another), the repository's
+resolved implementer fill (or the one `implementer=<id[@effort]>` pins; the run
+stops if that pin is unavailable, never swapping in another), the repository's
 default branch, `autonomous` merge, the `full` scheduler mode (or the one
 `scheduler=narrow|off` names), and the drafted plan, with
 no questions at any point. Invoking it is the

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

@@ -6,7 +6,7 @@ metadata:
   workflow-role: coordinator
 dependencies:
   - resolve-release
-release-version: 0.47.0
+release-version: 0.48.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.47.0
+release-version: 0.48.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.47.0
+release-version: 0.48.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.47.0
+release-version: 0.48.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.47.0
+release-version: 0.48.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.47.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Document and Image Authenticity

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

@@ -12,7 +12,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.47.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Fraud Detection

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
   fraud rule discovery (fraud-detection) or TLD / MCC-miscoding
   clusters (tld-detection).
-release-version: 0.47.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Payment Analysis

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

@@ -5,7 +5,7 @@ description: >
   and investigate selected merchants' authorization, settlement and disputes,
   including descriptor mapping and overlapping exports. Portfolio-level payment
   overviews belong to payment-analysis; fraud rule discovery belongs to fraud-detection.
-release-version: 0.47.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Portfolio 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-detection).
 disable-model-invocation: true
-release-version: 0.47.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Similar Domain

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

@@ -6,7 +6,7 @@ description: >
   patterns, with USD and BIN-country currency views, group profiles and priorities.
   Not payment-analysis, fraud-detection, or website research.
 disable-model-invocation: true
-release-version: 0.47.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # TLD detection

package/skills/engineering/resolve-issues/scripts/discover-models.mjs

@@ -1,9 +0,0 @@
-// Thin wrapper: canonical ownership lives in harness-runtime.
-export * from '../../harness-runtime/discover-models.mjs'
-
-import { runCli } from '../../harness-runtime/discover-models.mjs'
-import { isMainModule } from '../../engineering-runtime/scripts/main-module.mjs'
-
-if (isMainModule(import.meta.url)) {
-  process.exit(runCli(process.argv.slice(2)))
-}

package/skills/engineering/resolve-issues/scripts/model-catalog.mjs

@@ -1,9 +0,0 @@
-// Thin wrapper: canonical ownership lives in harness-runtime.
-export * from '../../harness-runtime/model-catalog.mjs'
-
-import { runCli } from '../../harness-runtime/model-catalog.mjs'
-import { isMainModule } from '../../engineering-runtime/scripts/main-module.mjs'
-
-if (isMainModule(import.meta.url)) {
-  process.exit(runCli(process.argv.slice(2)))
-}