f299bae77b
Add OPS repo presence detection in supervisor-run.sh with degraded mode support: - Detect if OPS_REPO_ROOT is missing and log WARNING message - Set OPS_REPO_DEGRADED=1 flag and configure fallback paths - Bundle minimal knowledge files as fallback for degraded mode - Update formula to use OPS_KNOWLEDGE_ROOT, OPS_JOURNAL_ROOT, OPS_VAULT_ROOT - Support local vault destination and journal fallback when ops repo absent Knowledge files bundled: disk.md, memory.md, ci.md, git.md, dev-agent.md, review-agent.md, forge.md The supervisor now runs with full functionality when ops repo is available, or gracefully degrades to local paths when absent, making the failure mode explicit rather than silent.
25 lines
750 B
Markdown
25 lines
750 B
Markdown
# Forgejo Operations — Best Practices
|
|
|
|
## Forgejo Issues
|
|
|
|
When Forgejo operations encounter issues:
|
|
|
|
### API Rate Limits
|
|
- Monitor rate limit headers in API responses
|
|
- Implement exponential backoff on 429 responses
|
|
- Use agent-specific tokens (#747) to increase limits
|
|
|
|
### Authentication Issues
|
|
- Verify FORGE_TOKEN is valid and not expired
|
|
- Check agent identity matches token (#747)
|
|
- Use FORGE_<AGENT>_TOKEN for agent-specific identities
|
|
|
|
### Repository Access
|
|
- Verify FORGE_REMOTE matches actual git remote
|
|
- Check token has appropriate permissions (repo, write)
|
|
- Use `resolve_forge_remote()` to auto-detect remote
|
|
|
|
### Prevention
|
|
- Set up monitoring for API failures
|
|
- Rotate tokens before expiry
|
|
- Document required permissions per agent
|