feat(edge): add HTTP command and message endpoints

[Jorel97]

Closes #22
/claim #22

Implements the Edge HTTP Server bounty endpoints while preserving the existing /healthz and /api/v1/* routes.

What changed:

• Adds /api/health and /api/status for edge readiness/status introspection.
• Adds /api/command plus backwards-compatible /api/v1/command handling.
• Adds /api/message plus /api/v1/message handling.
• Wires command/message POSTs into pkg/bus.MessageBus as inbound messages with useful metadata.
• Keeps the existing edge.NewServer(cfg) call shape working, while allowing edge.NewServer(cfg, msgBus) for production bus integration.
• Adds focused tests for health/status, command publishing, message publishing, and invalid JSON handling.
• Includes a small deterministic pkg/gene tie-breaker fix so the repository-wide Go suite can pass while reviewing the bounty branch.

Verification:

• go test ./pkg/edge
• go test ./cmd/picoclaw ./pkg/bus ./pkg/edge
• go test ./...
• git diff --check

Reviewer note: after the maintenance update, the branch passed go test ./..., including pkg/edge, pkg/gene, and pkg/logger.

[Jorel97]

Maintenance update pushed after the issue-thread validation discussion:

• added deterministic gene-selection tie-breaks when candidate scores are equal (score desc, then confidence desc, then verification count desc)
• this removes the unrelated full-suite blocker in pkg/gene while leaving the Edge HTTP Server scope intact

Validation after the update:

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

[Jorel97]

Claim/validation refresh for bounty #22:

• PR body now explicitly uses Closes #22 and /claim #22 for bounty association.
• Re-ran validation on the current branch:
  • go test ./pkg/edge ./pkg/bus ./cmd/picoclaw -> passed
  • go test ./... -> passed
  • git diff --check -> passed

No contributor-side changes are pending unless maintainers want a different edge API shape.