#102 ci: surface unknown mneme-check verdicts

[Anonymous]

Originally created by: TheoV823

• Fixes the self-check trustworthiness gap where UNKNOWN verdicts appeared in rows but were omitted from the summary.
• Adds an unknown counter to the sticky PR comment.
• Includes raw CLI output for UNKNOWN results in Details.
• Emits a warning callout when any verdict is UNKNOWN.
• Leaves PASS/WARN/FAIL and warn-mode behavior unchanged.
• Does not change core enforcement, retrieval, benchmark, or CLI semantics.

Validation caveat

Because this PR only changes .github/workflows/mneme-check.yml, which is outside the current mneme-check path filter, the PR run exercised the workflow and no-files-in-scope branch but did not exercise UNKNOWN rendering in GitHub. UNKNOWN rendering was validated by local shell simulation for mixed PASS/FAIL/UNKNOWN, all PASS, and all UNKNOWN scenarios.

Whether .github/workflows/* should be added to the mneme-check path filter as an automation-governance surface is tracked as a separate follow-up issue, not this PR.

[Anonymous]

Originally posted by: github-actions[bot]

mneme self-governance check

Mode: warn - verdicts are visible but do not block merge. Rollout plan: .mneme/README.md.

No files in scope. Filter: mneme-project-memory/mneme/, docs/adr/, .mneme/, site/, scripts/.

[Anonymous]

Ticket changed by: TheoV823

• status: open --> closed