Skip to content

docs: harden herdr pi team from HUB dogfood - #3

Closed
adihex wants to merge 5 commits into
mainfrom
improve/herdr-pi-team-dogfood
Closed

adihex wants to merge 5 commits into
mainfrom
improve/herdr-pi-team-dogfood

Conversation

@adihex

@adihex adihex commented Aug 25, 2026

Copy link
Copy Markdown
Owner

Summary

Audits and updates the canonical skills/herdr-pi-team/SKILL.md from the real HUB-246, HUB-247, and HUB-248 dispatch. Adds live CLI preflight, model/footer verification, integration/version remediation, nonblocking prompt semantics, same-worktree resume, worktree readiness, source-copy collision, and cleanup guidance. Adds the durable evidence record at dogfood/hub-246-248.md.

Findings and exact changes

  1. pi-team-herdr launch --workspace <existing-id> returned workspace setup failed, while native herdr agent start --pane worked. Root cause is not conclusively proven; the skill now treats it as a wrapper/setup-path mismatch, stops blind retries, and gives native fallback.
  2. Requested cvf/luna • medium became openai-codex/gpt-5.6-luna • high after an auto-loaded preset extension. Launch now requires checking the live footer provider/model/thinking/context before work proceeds.
  3. Preset/configuration changes require restart. The skill gives a same-worktree pi --continue procedure and preservation checks.
  4. herdr agent prompt ... --wait timed out at 30 seconds while prompts were accepted and workers continued. The skill distinguishes control-plane wait timeout from worker failure and recommends nonblocking submission for long work.
  5. Current wrapper help requires status --manifest MANIFEST; bare status is removed from the documented contract. Native herdr agent list is the live-status path.
  6. Current installation was verified with herdr 0.8.2, pi-team-herdr 0.2.0, Pi integration v8. The skill adds herdr integration status/doctor preflight and says to install Pi integration and restart agents when stale.
  7. OMP/Pi share an extension directory, so herdr integration install omp can refuse. The skill documents the collision without forcing migration.
  8. Workmux post_create pnpm install failed on canvas/pangocairo; --no-hooks worktrees lacked node_modules until later. The skill separates setup from readiness and requires concrete dependency/readiness evidence.
  9. Three agents died after extension/config changes and recovered with --continue in the same worktree. The skill explicitly preserves the session/worktree and verifies workspace, state, footer, and artifacts before resuming.
  10. Duplicated work-profile skill copies caused collision warnings. The skill says to resolve the canonical repository source and avoid installed/generated copies.

Validation

  • herdr --versionherdr 0.8.2
  • pi-team-herdr --version0.2.0
  • herdr integration status → Pi current v8; OMP not installed; no forced migration
  • pi-team-herdr launch --help, status --help, and herdr agent prompt --help inspected and saved under /tmp/*-help-final.txt
  • Scripted assertions confirmed --workspace, --manifest MANIFEST, and --wait contracts
  • Skill metadata/structure audit passed; 125 lines, under 500-line limit
  • git diff --check passed
  • No product code or team.ts changed

Golden scenarios

G1–G10 do not apply: this PR changes only documentation and a durable dogfood evidence note, not team.ts or its runtime. The skill explicitly records this boundary. If runtime changes later, run the full pi-dogfood-os golden gate and retain its JSON result.

Risks and restart implications

  • CLI behavior can change; the skill deliberately requires live help/version checks rather than relying on static syntax.
  • The model/footer check is manual because the wrapper does not expose a trustworthy provider override result.
  • Integration changes affect already-running agents only after restart. Existing agents need restart when Pi integration, preset, or extension configuration changes; this PR itself does not require restarting current agents.
  • Push from the local checkout was denied because the configured origin HTTPS credential belongs to abalak-cv while repository ownership is adihex. The branch is available locally and PR creation should use the authenticated adihex account or a fork/credential with push permission.

@adihex

adihex commented Aug 28, 2026

Copy link
Copy Markdown
Owner Author

Closing because PR #4 supersedes its herdr-pi-team documentation changes with tested wrapper implementation and compatibility checks.

@adihex adihex closed this Aug 28, 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.

2 participants