vouchington-tooling 0.4.2 → 0.5.1

package/dist/ast-grep-examples/index.mjs

@@ -86,7 +86,7 @@ function scanScopedRule(loaded, root, languageGlobs, execute) {
     }
     fs.copyFileSync(loaded.ruleFile, join(root, 'rule.yml'));
     fs.writeFileSync(join(root, 'sgconfig.yml'), yamlDump({ languageGlobs }));
-    const result = execute(['scan', '--rule', 'rule.yml', '--config', 'sgconfig.yml', '--json', '--no-ignore', '--hidden'], root);
+    const result = execute(['scan', '--rule', 'rule.yml', '--config', 'sgconfig.yml', '--json', '--no-ignore', 'hidden'], root);
     if (result.status === null || result.status > 1)
         throw new Error(`ast-grep scan failed (exit ${result.status ?? 'signal'}): ${result.stderr ?? ''}`);
     const found = new Set(result.stdout?.trim()

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vouchington-tooling",
-  "version": "0.4.2",
+  "version": "0.5.1",
   "description": "Vouchington CLI and extractable tooling libraries.",
   "homepage": "https://github.com/vouchington/vouchington-tooling/tree/main/packages/vouchington-tooling#readme",
   "bugs": {

package/skills/retrospective-distill/SKILL.md

@@ -14,11 +14,17 @@ Use when completed retrospectives or journals should become durable follow-up wo
 3. Verify each candidate against the current base and search existing issues and open changes before
    drafting. Skip work that is complete, explicitly rejected, or already covered.
 4. Draft self-contained issues with the problem, concrete proposed work, relevant areas, and
-   evidence embedded in the body. Route every authorized creation through
+   validation. Route every authorized creation through
    [github-issue](../github-issue/SKILL.md), including its repository gate, label approval, and
    denied-external tracking behavior.
 5. Archive only records that were fully processed under the repository's retention rules; report
    created, updated, skipped, and deferred themes with reasons.
 
+Use source records only for local verification and leave them in the repository's approved journal
+or retention system. Public issue bodies contain only the minimum bounded facts or redacted summaries
+needed to establish the problem, proposed work, relevant areas, and validation. Never embed
+unredacted logs, command output, environment details, provider payloads, or transcript content.
+
 This skill supplies no journal API, issue repository, labels, milestones, archival command, or
-approval model. A consumer wrapper provides those details.
+approval model. Consumer wrappers cannot weaken this export boundary; they provide only those local
+details.