Spec: Dev environment with shared credentials and staging relay

[agent-relay]

Summary

Specify shared development environment infrastructure for:

• Agent git operations (consistent credentials, no per-token management)
• Dashboard preview functionality (per-PR deployments)
• Staging relay daemon for previews

Clarifying Questions

1. Infrastructure: What does shared dev environment require?

   • Single server or containerized (Docker)?
   • Cloud platform (AWS, GCP, etc.)?
   • Configuration management (Terraform, Ansible)?

2. Staging Relay: Single daemon instance for all agent previews?

   • Isolated from production?
   • Shared database or separate?
   • Load capacity requirements?

3. Credentials Management:

   • How to safely store shared git credentials?
   • Rotation policy (weekly, monthly)?
   • Audit trail for credential usage?
   • Access control (who can use shared env)?

4. Agent Access & Setup:

   • URL/hostname for agents to connect?
   • Environment variables needed?
   • Setup documentation and automation?
   • Testing the shared environment?

5. CI/CD Integration:

   • Trigger per-PR deployments automatically?
   • GitHub Actions workflow?
   • Rollback procedure?
   • Monitoring and alerting?

Success Criteria

• Agents can push code without individual git token management
• Dashboard previews available and working for all PRs
• Credentials safely managed with rotation policy
• Setup documented for team
• Deployment automated (GitHub Actions trigger)
• No single points of failure

Related

• Beads task: bd-dev-env-spec
• Trail: traj_2pqscusnnlsl

[khaliqgant]

FYI @willwashburn

I wanted to release the agent so had them open this as a placeholder so it don't get lost.