geomind_code/dev_docs
22
0
Fork 0
Code Issues 10 Pull requests 1 Projects Releases 2 Packages 1 Wiki Activity Actions

Add deps.txt maintenance guide and WASM CI patterns to skills #18

New issue
Open
opened 2026-02-17 19:24:34 +00:00 by mik-tf · 0 comments
mik-tf commented 2026-02-17 19:24:34 +00:00
Member
Copy link

Context

During CI fixes on hero_books (PR #57) and hero_archipelagos (PR #14), we discovered recurring patterns that are not yet documented in the skills. hero_books CI broke because deps.txt referenced a crate that had migrated to a different repo (herolib_osis → hero_rpc_osis). hero_archipelagos CI had 130 consecutive failures partly due to fragile wasm-pack path listings and a package name hyphen/underscore mismatch.

Goals

  • Add deps.txt maintenance rules to forge_ci skill (what to update after dependency migrations)
  • Add WASM compilation strategy guidance to forge_ci (cargo check vs wasm-pack)
  • Add new CI issue rows: stale deps.txt, package name mismatches, stale generated code
  • Add deps.txt sync checklist to hero_coderoot skill
  • Document the deps.txt file format and how CI uses it
## Context During CI fixes on hero_books (PR #57) and hero_archipelagos (PR #14), we discovered recurring patterns that are not yet documented in the skills. hero_books CI broke because deps.txt referenced a crate that had migrated to a different repo (herolib_osis → hero_rpc_osis). hero_archipelagos CI had 130 consecutive failures partly due to fragile wasm-pack path listings and a package name hyphen/underscore mismatch. ## Goals - Add deps.txt maintenance rules to `forge_ci` skill (what to update after dependency migrations) - Add WASM compilation strategy guidance to `forge_ci` (cargo check vs wasm-pack) - Add new CI issue rows: stale deps.txt, package name mismatches, stale generated code - Add deps.txt sync checklist to `hero_coderoot` skill - Document the deps.txt file format and how CI uses it
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
development
development_mik
main
latest
v1.0.0
v0.1.0
v0.0.1-rc1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
geomind_code/dev_docs#18
No description provided.