Repository navigation
chore(upstream): sync latest pstack - #48
Conversation
3metaJun
left a comment
There was a problem hiding this comment.
I found two actionable issues; I do not recommend merging yet.
-
[blocking] The upstream validation job still checks out the old pstack commit.
profiles/upstreams.jsonnow pins11713c683fe4add4fd403ea880580abbc9e0875f(line 4), but.github/workflows/validate.ymlstill passesref: 2cbf58508f40de470d7490b55c51d71241928fa2to the checkout step. Theupstreamcheck therefore fails with “Source checkout is at 2cbf585..., profile pins 11713c...”, as seen in the current PR checks. Update the workflow ref (and any equivalent source pin) together with this sync. -
[compatibility] This PR removes two guide pages from the guide index without updating existing inbound links.
docs/guide/README.mdremoves11-mixed-harness.mdand12-claude-code-routing.md, butREADME.md:131,README.md:553, anddocs/harness-adapters.md:130,175still link to those paths. Those links become 404s in the published repository/package. Either retain the pages or update/remove every inbound reference.
The other checks are green, but the upstream job is failing and the stale links are a user-facing regression. Please address these before merge.
|
Addressed the blocking review finding: The two guide pages mentioned in the review are still present in the repository and package; the guide index no longer lists them, but existing inbound links remain valid. No link changes were needed. The full local suite passed before this CI-only change; waiting for the updated CI run before merge. |
The pstack upstream has advanced, leaving mstack's bundled skills, guides, automations, and runtime metadata behind.
This updates the pstack pin to 11713c6, imports the new ketchup skill, refreshes the tracked upstream artifacts and manifest, and preserves mstack-specific portability adaptations. Cursor-only frontmatter is removed from the imported skill.
Verification:
Agent: gpt-5 via pi