[skill] Propose issue-ledger-followup for amendment-aware work loops

[auscaster]

Objective

Propose a portable issue-ledger-followup skill that turns one living work issue ledger into the next high-signal machine update or maintainer handoff packet.

Why

We want one issue per unit of work. Human amendments in that same thread should sharpen the next run instead of fragmenting context across dispatch UIs, separate proposal issues, or hidden memory.

Desired Contract

• Input is portable subject memory, with GitHub issue threads as one adapter surface.
• The skill reads the work issue ledger plus trusted amendment comments.
• It emits a bounded follow-up packet for one next action: clarifying comment, approval request, maintainer handoff, or draft PR refresh request.
• It must preserve receipts and keep the issue thread as the human-visible ledger.
• It should stop at an explicit handoff boundary, not silently publish.

What We Want To Learn

• Whether skill-lab now treats the issue thread as the canonical living ledger.
• Whether the generated proposal stays tight around subject memory, outbox, receipts, and handoff boundaries.
• Whether a later human amendment comment in this same issue cleanly retriggers the lane and sharpens the proposal.

Constraints

• Prefer one skill with a small, legible surface.
• No provider-locked nouns in the core contract.
• Keep the proposal grounded in the current runx / aster vocabulary.

[auscaster]

runx skill lab

• Objective: Propose a portable issue-ledger-followup skill that turns one living work issue ledger into the next high-signal machine update or maintainer handoff packet.
• Status: proposal_refreshed
• Proposal: issue-ledger-followup (status=proposed)
• Summary: Read portable subject memory plus one canonical work-thread ledger and trusted amendment comments, then emit exactly one bounded follow-up packet without publishing it.
• Ledger revision: 95ce832dc0daf6e4
• Workflow run: https://github.com/nilstate/aster/actions/runs/24782040314

Changed in this refresh

• Surfaced the substantive proposal payload from the latest design run instead of a slug-only status stub.
• Acceptance checks surfaced: 9.
• Publication remains gated until skill-lab.publish is explicitly authorized on the same work issue.

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]

Thread Teaching Record

Kind: lesson
Summary: The live rerun proved the issue-ledger loop works, but the surfaced proposal collapsed to a thin stub even though the internal steps produced substantive findings.
Recorded By: kam
Target Repo: nilstate/aster
Subject Locator: nilstate/aster#issue/113
Notes:

• Keep the single-issue ledger model.
• On the next refresh, surface the actual findings from this run instead of only the slug summary.
• Carry forward the concrete design points already produced internally: portable subject memory plus subject_locator, one bounded next-action packet, stop-before-publish, and the open questions around trusted amendments, retrigger policy, packet-shape reuse, and publication surface.
• If a repo-read follow-up is required to verify existing packet or schema reuse, say that plainly rather than implying the proposal is final.
• In the refreshed issue update, call out exactly what changed because of this amendment comment so we can verify the living-ledger loop end to end.

[auscaster]

Thread Teaching Record

Kind: lesson
Summary: The live skill-lab rerun is still surfacing a thin status stub even though the artifact contains a substantive proposal payload.
Recorded By: kam
Target Repo: nilstate/aster
Subject Locator: nilstate/aster#issue/113
Notes:

• I inspected workflow run 24759465675 and the generated promotion markdown still only surfaces Summary: issue-ledger-followup.
• The same run's result.json.execution.stdout already contains substantive structured output: skill_spec, execution_plan, harness_fixture, and acceptance_checks.
• On the next refresh, surface the actual proposal findings in the issue update and promotion draft instead of the slug-only summary.
• At minimum, carry forward the concrete skill summary, the portable inputs (subject_locator, subject_title, subject_body, subject_memory, outbox_entry, allowed_next_actions, trusted_amendment_rule, stop_before_publication), the bounded chain steps (read-issue-ledger, draft-followup-packet, assemble-handoff-packet), and the thin-stub regression guard.
• If the proposal materializer still cannot safely project those fields, say that plainly in the issue update as a materialization gap instead of implying the proposal was fully refreshed.
• In the refreshed issue update, add a short Changed in this refresh section so we can verify the amendment-aware living-ledger loop end to end.

[auscaster]

Thread Teaching Record

Kind: lesson
Summary: The stale runx skill-path cutover is now deployed; rerun the same work issue ledger and surface the real proposal payload.
Recorded By: kam
Target Repo: nilstate/aster
Subject Locator: nilstate/aster#issue/113
Notes:

• The live workflow now points at design-skill, request-triage, and issue-triage, matching the current runx skill names on main.
• Rerun the same ledger from this issue thread.
• Keep the prior amendment requirements: surface the substantive proposal findings instead of the slug-only stub.
• In the refreshed issue update, include a short Changed in this refresh section so the issue thread shows what the new run actually fixed.

[auscaster]

Thread Teaching Record

Kind: lesson
Summary: The skill-lab request-output gating fix is now deployed; rerun once more and ensure the rolling issue status comment refreshes on success.
Recorded By: kam
Target Repo: nilstate/aster
Subject Locator: nilstate/aster#issue/113
Notes:

• The previous successful run surfaced the real proposal content in artifacts, but the rolling machine status comment stayed stuck on run_failed because objective_present never propagated.
• Rerun the same issue ledger.
• Keep the same substantive proposal payload.
• The live success criterion for this refresh is: the rolling runx skill lab comment updates to a success state and points at the new workflow run.

[auscaster]

Thread Teaching Record

Kind: lesson
Summary: The richer skill-lab issue-update surface is now deployed; rerun once more so the rolling machine comment carries proposal signal and refresh deltas.
Recorded By: kam
Target Repo: nilstate/aster
Subject Locator: nilstate/aster#issue/113
Notes:

• Keep the same issue-ledger objective and bounded handoff shape.
• The success criterion for this refresh is: the rolling runx skill lab comment reports proposal identity, summary, and a short Changed in this refresh section, not just status.