Skip to content

Consolidate harness boundaries and remove architectural drift #35

Description

@thisguymartin

Make pstack-flex a portable shared skill system with explicit harness integration boundaries. This cleanup accompanies #33 and preserves the independently merged OpenRouter and project-model work.

  • Keep upstream skill bodies and one shared skills tree.
  • Centralize parent capabilities, model-sheet paths, child markers and journal identity; keep lane/provider execution separate.
  • Remove duplicated host setup recipes and routing prose; preserve global/project replacement and exact requested model/effort behavior.
  • Consolidate current docs and delete completed plans, stale probe logs and unused compatibility artifacts.
  • Run baseline/head behavior comparisons, full checks, packaging validation and adversarial review.
  • Consolidate Separate shared pstack workflows from harness and lane adapters #33 plus cleanup into one commit on main b49b15d without squashing upstream/OpenRouter history.

Installed user-surface verification stays a separate mandatory gate. No merge, tag, release or rollout until the exact candidate passes in each affected harness. Missing evidence leaves #33 draft.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions