Skip to content

Add dependency upgrade plan skill - #126

Closed
RYDE-PLAY wants to merge 80 commits into
runxhq:mainfrom
RYDE-PLAY:ryde-play/dep-upgrade-plan
Closed

Add dependency upgrade plan skill#126
RYDE-PLAY wants to merge 80 commits into
runxhq:mainfrom
RYDE-PLAY:ryde-play/dep-upgrade-plan

Conversation

@RYDE-PLAY

Copy link
Copy Markdown
Contributor

Adds a governed dep-upgrade-plan skill for #53.\n\nSummary:\n- reads package-lock.json plus advisory and constraint facts\n- emits ranked plan entries with exact pkg/from/to/risk/breaking fields and changelog\n- refuses when all candidate upgrades violate constraints\n- includes sealed and refusal harness cases plus fixture evidence\n- registers the skill in official skill locks\n\nLocal checks run:\n- runx skill inspect ./skills/dep-upgrade-plan --json\n- runx harness ./skills/dep-upgrade-plan --receipt-dir /tmp/frantic53-harness-receipts --json\n- node scripts/check-upstream-skill-bindings.mjs

auscaster and others added 30 commits June 19, 2026 19:55
default to the /internal/thread-outbox pending cursor (drops the fragile client cursor-cache that re-walked history on a fresh runner) and listen for a board-sync repository_dispatch so the venue can trigger the drain low-latency.
a no-ua, no-browser-headers, http1.1 client is an obvious bot signature. the fetch tool now presents a current chrome ua + the browser header set and negotiates http2 with gzip/brotli, applied as overridable defaults. configurable via RUNX_HTTP_USER_AGENT and RUNX_HTTP_BROWSER=0; the anthropic and registry transports stay plain; all transport guards unchanged. tls (ja3/ja4) and http2 fingerprint matching are out of scope.
Conventional follow-up for the pushed lockfile refresh.
Adds the dependency-cve-audit runx skill and registers it in the official catalog.

Verified:
- CI green on PR runxhq#82
- node --check skills/dependency-cve-audit/run.mjs
- runx doctor skills/dependency-cve-audit --json
- runx harness skills/dependency-cve-audit --receipt-dir <tmp> --json
- packages/cli/src/skill-refs.test.ts
Adds the structured-extraction runx skill and completes the paid follow-up integration work.

Maintainer cleanup added:
- deterministic tool fixture for structured.extract
- SKILL.md frontmatter for official catalog generation
- official skill lock/Rust table/catalog allowlist entries

Verified:
- CI green on PR runxhq#80
- local merge simulation after runxhq#82
- node --check skills/structured-extraction/tools/structured/extract/run.mjs
- runx doctor skills/structured-extraction --json
- runx harness skills/structured-extraction --receipt-dir <tmp> --json
- runx dev tools/structured/extract --json with RUNX_PROJECT_DIR set to the skill root
- packages/cli/src/skill-refs.test.ts
@RYDE-PLAY
RYDE-PLAY force-pushed the ryde-play/dep-upgrade-plan branch 3 times, most recently from 60e04c2 to 7a1f34b Compare June 23, 2026 05:24
Replace the frantic-specific event-replay driver with a generic, stateless
reconcile engine: consume a tenant's desired thread state, diff against live
GitHub, apply only the difference via the provider primitives. Drop the cursor
and the frantic_thread_outbox translator; generalize label ensure.
Reconcile read each issue thread once per run (state, labels, comment markers)
and write only actual differences, instead of re-fetching the whole thread per
comment. Steady state is now one read per thread and zero writes; cut redundant
per-run observations to newly-created threads only.
@RYDE-PLAY
RYDE-PLAY force-pushed the ryde-play/dep-upgrade-plan branch 3 times, most recently from c5668a2 to d316216 Compare June 24, 2026 01:12
@RYDE-PLAY
RYDE-PLAY force-pushed the ryde-play/dep-upgrade-plan branch from d316216 to fe0a77c Compare June 24, 2026 01:17
@auscaster

Copy link
Copy Markdown
Collaborator

Closing to consolidate: we're reviewing one PR per contributor and yours is #277 (rollback-judge). Most of these predate the July skill-tree rename, which was our break, not yours, so they can't rebase cleanly anyway.

@auscaster auscaster closed this Aug 10, 2026
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.

4 participants