learnlisted

# Learning and retrospective capture ## Purpose Record evidence-bound learning without becoming a policy, lifecycle, or destination owner. ## When to use `learn` is periodic or explicitly invoked for repeated review findings, blocker or major workflow-process findings, failed release or adapter smoke, accepted postmortem action, explicit maintainer request, incident response, contributor observation, cadence, or another stated trigger. capture the lesson immediately, create a scheduled follow-up, or record an explicit no-learn rationale. It blocks downstream only when a higher-priority artifact explicitly makes it blocking. ## When not to use Do not run it by default, manufacture patterns, or bypass a destination owner. ## Inputs to read Read the trigger, named artifacts, relevant prior learning, and the smallest decision-bearing evidence. ## Outputs Produce a session record after Frame, justified topic guidance, owner-bound routes, and reconciled owner-result identities. Pre-session closeout remains in a contributor-visible tracked or review-visible surface owned by the trigger source. ## Handoff - Normal next stage: none; record the session or route result and stop. - Conditional next stages: send owner-bound work to the applicable skill or process; use `workflow` for governed routing. ## Operations and profiles Select exactly one operation: - `run-learn-session` (`LR1-session`): record a triggered session, topic effects, and owner-bound routes. - `record-lea