[velzepooz]

Summary

• Publish v1.14.1 metadata for the already-merged public-clone cleanup (fix(docs): keep Action records out of clones #31).
• Align both telemetry version literals, README example, test and changelog.
• No detector pin, scan logic or gate changes.

Verification

• 20 focused Bats tests passed; README candidate test passed.
• make verify-clone: clones clean on the committed release candidate.
• Full local macOS Bats remains 120/122 because of pre-existing Bash 3.2 and BSD grep incompatibilities. GitHub CI on Linux validates the full suite; release workflow validates published rule pages.

After merge, push immutable v1.14.1 at main; release workflow moves floating v1 only after the live rule-page gate passes.

Amp thread: https://ampcode.com/threads/T-01a0e497-3af5-777e-a9af-278e87e7c9d6

[github-actions]

SkillTrust — Clean — no findings

SkillTrust check passes — no findings.

If this check is required, failure blocks merging.

Comparison off; new, existing and fixed status is unknown.

Next: No finding remediation is needed in the scanned scope. Review the rest of the PR as usual.

Current findings (0)

None.

Grades for the current scan

Grades describe findings, not whether this check fails. The policy above determines the check result.

Axis	Grade
Security	A
Permission hygiene	A
Transparency	A

Scan details and scope

Run	Value
Scope	tests/fixtures/clean-repo
Checkout	Workflow checkout
Engine	skill-detector 0.12.1
Mode	Gate policy
Files scanned	1
Comparison	Off

Supported boundary

SkillTrust checks supported agent configuration files in the selected scope. A clean result means no supported rule matched; it is not a guarantee that the repository is safe.

Complete result

The validated, unmodified JSON is retained at the scan-json-path output. To retrieve it after the job, upload that path with actions/upload-artifact; see the Action docs.

---

SkillTrust Action docs · scan-action@v1 · Detector 0.12.1