[skill] Add a collaboration issue distillation skill

[auscaster]

Objective

Add a governed runx skill proposal for a collaboration issue distillation skill that turns a bounded GitHub issue thread into a reusable approval packet and maintainer recap before any publish or build gate proceeds.

Why It Matters

We want issue review to train the operator. Human rationale should become explicit, rebuildable context rather than hidden prompt sprawl. This run should tell us whether skill-lab can produce a useful design for issue-shaped learning and approval work.

Constraints

• proposal only, no implementation code
• output stays under docs/skill-proposals/
• skill output should be markdown/json artifacts, not direct GitHub mutation
• treat issue comments and GitHub Actions receipts as canonical evidence; derived memory must stay rebuildable
• call out approval boundaries explicitly and keep any publish surface draft-only
• acceptance checks should cover missing rationale, conflicting comments, and stale evidence

Evidence

• state/thread-teaching.json is the current derived teaching surface
• docs/philosophy.md says repeated work should become explicit skills, not prompt sprawl
• docs/operations.md says every lane has an approval mode and memory effect
• collaboration issues are becoming a core review surface for bounded approvals

[auscaster]

Amendment for this proposal:

• hard-cut the core contract to subject_locator, subject_memory, and publication_target; GitHub issue is only one adapter surface, not the core noun
• keep the GitHub issue thread as the living ledger for the GitHub adapter, but explicitly explain how the same skill can run from chat or CLI/agent context against the same contract
• separate canonical evidence, distilled findings, and publish/build readiness instead of collapsing them into one packet
• add at least one non-GitHub fixture that proves the skill can distill the same bounded collaboration subject outside GitHub while preserving the same approval semantics
• call out how maintainer amendments in the living ledger feed the next run without becoming hidden prompt-only state

[auscaster]

runx skill lab

• Objective: Add a governed runx skill proposal for a collaboration issue distillation skill that turns a bounded GitHub issue thread into a reusable approval packet and maintainer recap before any publish or build gate proceeds.
• Status: draft_pr_refreshed
• Draft PR: #111
• Ledger revision: 63983af249f7f32a
• Workflow run: https://github.com/nilstate/aster/actions/runs/24724235042

Reply in this work issue with maintainer amendments, constraints, or teaching notes and skill-lab will refresh the same proposal from the same work ledger.

[auscaster]

Kind: publish_authorization
Summary: Refresh the single rolling skill-lab draft PR for this issue from the same work ledger.
Recorded By: kam
Target Repo: nilstate/aster
Subject Locator: nilstate/aster#issue/110
Applies To: skill-lab.publish
Invariant: Refresh PR #111 only; do not open a second draft PR for this issue.
Decision: skill-lab.publish = allow | refresh the existing rolling draft PR from the same issue ledger