Skip to content

Add steward to the per-agent AGENTS map (8627/9627) #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TadMSTR merged 1 commit into from
Aug 18, 2026
Merged

Add steward to the per-agent AGENTS map (8627/9627) #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions ecosystem.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,19 @@ const AGENTS = {
writer: { httpPort: 8623, metricsPort: 9623 },
research: { httpPort: 8624, metricsPort: 9624 },
harlock: { httpPort: 8625, metricsPort: 9625 },
// steward — the config-owning agent (vikunja#350, build
// steward-config-agent-2026-08). Its git job is narrow by design: branch,
// commit, push and open a PR on host-forge-scripts carrying a config
// proposal. It holds no merge, release, tag or publish verb — enforced by a
// tool_allowlist in steward-agent.yml rather than a denylist, so a future
// githost-mcp release cannot add a write verb steward silently inherits.
//
// 8627/9627, not the contiguous 8626: that is backrest-mcp. 8625/9625 stay
// reserved to harlock rather than being reclaimed here — harlock's
// decommission (vikunja#270) is only through Phase 0 and reassigning a port
// out from under a half-removed agent is how two services end up racing for
// one bind. Renumber both together when that decommission finishes.
steward: { httpPort: 8627, metricsPort: 9627 },
};

function buildApp(agentId, ports) {
Expand Down