hermes - 💡(How to fix) Fix Skill proposal: auditable decision trail for long autonomous coding runs

Source pattern: cursor/plugins pstack at 21327be, especially show-me-your-work and figure-it-out.

Hermes adaptation:

• Add a lightweight optional decision-trail artifact for long-running coding/kanban/cron work.
• Default local path could be .hermes/audit/<task-or-run>.tsv or a Kanban-run attachment, with columns: timestamp, phase, decision, why, evidence, result.
• Append-only by convention; evidence must point to a commit, PR, file:line, test log, screenshot, CI run, or generated artifact.
• Before final handoff, audit rows against actual tool outputs/session events and remove/update unsupported claims.
• Commit or attach the trail only when review trust requires it; keep it local for routine work.

Why this is useful:

• Hermes already runs unattended cron and Kanban workers. The user sees final summaries, but not always the decision trail behind pivots, rejected attempts, or partial verification.
• A small structured artifact improves reviewability without installing Cursor plugin runtime files.
• This complements, rather than replaces, issue #25380 worker-session mapping and issue #26742 claim verification.

Acceptance criteria:

• A bundled skill or coding-ops doc defines the TSV schema and when to use it.
• Kanban/cron/coding workflows can name the trail path in final summaries.
• The guidance requires evidence pointers and forbids aspirational or invented rows.
• At least one test or fixture validates log-row sanitation for tabs/newlines and spreadsheet formula prefixes if a helper script is added.