bounty: edge HTTP server for PicClaw

[Gavriel-lab]

I would like to work on the Edge HTTP Server for PicClaw bounty listed on the Clawland bounty board for $500.

Bounty board reference: https://clawland.ai/pages/bounty

Planned deliverable:

• Implement the required PicClaw Edge API endpoints:
  • POST /api/command
  • POST /api/message
  • GET /api/status
  • GET /api/health
• Keep compatibility with the existing /healthz and /api/v1/* routes where useful.
• Integrate command/message ingestion with the existing pkg/bus.MessageBus instead of only logging requests.
• Add focused pkg/edge tests for health/status responses, invalid JSON handling, command acceptance, and message bus publishing.

I will keep the first PR scoped to the Edge HTTP server surface and avoid changing unrelated agent behavior.

[Jorel97]

I'd like to work on this bounty as a focused compatibility PR.

Plan:

• keep existing /healthz and /api/v1/* routes working;
• add the requested /api/health, /api/status, /api/command, and /api/message endpoints;
• wire command/message ingestion into pkg/bus.MessageBus while preserving the existing edge.NewServer(cfg) call shape;
• add focused pkg/edge tests for health/status, invalid JSON, command acceptance, and message publishing.

[Jorel97]

Submitted implementation PR: #27

[attaboy11]

Linking my already-submitted implementation for this bounty: #19

Scope covered:

• adds POST /api/command and POST /api/message
• adds GET /api/status and GET /api/health
• keeps /healthz and /api/v1/* compatibility aliases
• wires command/message ingestion into pkg/bus.MessageBus
• adds focused pkg/edge tests for health/status, invalid JSON, command acceptance, and message publishing

Validation re-run today:

• go test ./...
• go vet ./...
• git diff --check

The PR is mergeable as of the latest check.

[Jorel97]

Status update for my submitted PR #27: it remains open and focused on the exact Edge HTTP Server bounty scope here. It preserves existing /healthz and /api/v1/* compatibility while adding /api/health, /api/status, /api/command, and /api/message, and wires command/message POSTs into pkg/bus.MessageBus with focused pkg/edge tests. Validation on the changed packages passed locally; the only full-suite blocker noted in the PR body is the existing unrelated pkg/gene ordering failure on main.

[attaboy11]

Reviewer-facing validation update for PR #19: I re-ran the full repository checks after the competing issue-thread updates. This branch is still mergeable and passes repository-wide validation, not just changed-package tests.\n\nValidation run on 2026-05-31:\n- go test ./... -> passed, including pkg/edge, pkg/gene, and pkg/logger\n- go vet ./... -> passed\n\nPR #19 also keeps the small deterministic pkg/gene selector tie-breaker fix in the branch, so the full suite is not blocked by the existing gene ordering failure while reviewing the Edge HTTP Server bounty.

[Jorel97]

Update for PR #27 after the full-suite validation discussion: I pushed a small deterministic pkg/gene tie-breaker fix so the branch now passes repository-wide validation, not only changed-package tests.

Validation after update:

• go test ./... -> passed, including pkg/edge, pkg/gene, and pkg/logger
• git diff --check -> passed

The Edge HTTP Server implementation remains scoped to this bounty: /api/health, /api/status, /api/command, /api/message, compatibility routes, and MessageBus integration.

[Gavriel-lab]

Submitted implementation PR for this bounty: #23

Scope covered:

• /api/health, /api/status, /api/command, and /api/message endpoints
• existing /healthz and /api/v1/* compatibility routes
• command/message ingestion through pkg/bus.MessageBus
• focused pkg/edge tests for health/status, invalid JSON, command acceptance, and message publishing

Validation:

• go test ./pkg/edge -> passed locally
• gofmt applied
• separate baseline fix for the existing pkg/gene full-suite blocker: fix: make gene selector ordering deterministic #26

I kept the bounty implementation isolated from the baseline gene fix so reviewers can evaluate the edge HTTP server scope cleanly.

[tanmayxchoudhary]

I have a PR ready for this bounty: PR #32. Would love to claim it.