feat(core/release): ship HTTP agents and release hardening#547
feat(core/release): ship HTTP agents and release hardening#547hermia-ai wants to merge 15 commits intojust-every:mainfrom
Conversation
7-sprint implementation plan covering: - Sprint 1-2: Foundation (env validation, HTTP agent rewiring with TDD) - Sprint 3-4: Agent defaults, branding, HCC metrics crate - Sprint 5: E2E validation, performance benchmarks, documentation - Sprint 6-7: Desktop GUI (CodePilot fork) + PicoClaw messaging gateway 32 tests/checks across unit, integration, regression, E2E, and performance. ECC adaptation deferred to v1.1. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Maintainer handoff (concise): Unblock checklist:
Exact blocker proof from this environment:
Evidence docs:
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 64258a3d84
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| if agent | ||
| .http_endpoint | ||
| .as_deref() | ||
| .is_some_and(|endpoint| !endpoint.trim().is_empty()) | ||
| { |
There was a problem hiding this comment.
Exclude HTTP-only agents from write-capable auto model selection
Marking any agent with a non-empty http_endpoint as runnable here makes it eligible in get_enabled_agents, which is used by format_subagent_command for /code as well as read-only commands. /code launches subagents with write enabled (default_read_only_for("code") == false), but HTTP dispatch only happens when read_only is true in execute_model_with_permissions (code-rs/core/src/agent_tool.rs, around lines 1727-1730). In practice, an HTTP-only agent (no local CLI binary) can now be auto-selected for /code and then fail at execution time with a command-not-found error.
Useful? React with 👍 / 👎.
Summary
This PR lands the Hermia deployment-hardening work to the furthest shippable state possible without
just-every/codeorigin push rights or production npm secrets.Included
code-rs/corewhile preserving write-mode subprocess semantics.scripts/wait-for-gh-run.shhardening with automatic GitHub REST API fallback for unauthenticated/public-repo monitoring.cross-platform-artifact-smokegate before publish.Release Evidence
docs/plans/release-evidence/2026-02-16-m1-http-subagents.mddocs/plans/release-evidence/2026-02-16-m2-deployment-validation.mdBlocker Proof (captured in evidence docs)
hermia-ai):push=falseand HTTPS 403 onjust-every/code.Permission denied (publickey).22087028099) but failed atValidate npm authdue missingNPM_TOKEN; downstream build/smoke/publish skipped.Handoff
Once maintainer write + secrets access is available, follow the final unblock checklist in:
docs/plans/release-evidence/2026-02-16-m2-deployment-validation.md