Skip to content

feat(skills): migrate shared-skill repair to operator notifications (SUP-3824 U2) - #217

Open
levineam wants to merge 2 commits into
mainfrom
SUP-3824/shared-skill-repair-notifications
Open

feat(skills): migrate shared-skill repair to operator notifications (SUP-3824 U2)#217
levineam wants to merge 2 commits into
mainfrom
SUP-3824/shared-skill-repair-notifications

Conversation

@levineam

Copy link
Copy Markdown
Owner

Summary

  • Migrate @jarvos/skills scheduled-repair human output onto the public @jarvos/runtime-kit operator-notification contract (SUP-3824 / plan unit U2).
  • Safe automatic holds (including unsafe_source), repairs, and resolutions emit NO_REPLY; owner decisions get plain-English direct messages with opaque event references and no raw codes, paths, or skill ids.
  • Attention durable status keeps reason codes with first-seen time and occurrence count for the shared-skills status/explain surface.

Stacking

Test plan

  • node --test modules/jarvos-skills/test/scheduled-repair.test.js modules/jarvos-skills/test/attention.test.js (14/14)
  • AE1: unsafe_source quiet + no raw codes in human output
  • AE2: owner decision message answers what/did/action/next + opaque reference
  • node --test modules/jarvos-runtime-kit/test/operator-notification.test.js
  • npm --prefix modules/jarvos-skills test (one pre-existing live-preflight failure: Codex CE fixtureTreeDigest mismatch on base; unrelated to U2)
  • CI green after U1 lands / CE fixture baseline is fixed

Paperclip

SUP-3824

…SUP-3824 U2)

Project scheduled-repair outcomes through the public runtime-kit notification
contract. Safe holds, automatic repairs, and resolutions stay quiet; owner
decisions get plain-English messages with opaque event refs and no raw codes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant