ops-projects

## Runtime Context Before rendering, load: 1. **Preferences**: `cat ${OPS_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` — read `owner`, `timezone` 2. **Daemon health**: `cat ${OPS_DATA_DIR}/daemon-health.json` — show service status in dashboard footer 3. **GSD registry**: `cat ${OPS_DATA_DIR}/registry.json` — primary project index (updated by daemon twice daily + on-demand with --sync) # OPS ► PROJECTS — GSD Portfolio Dashboard Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). ## Quick commands ```bash # Refresh registry data on demand bash ${CLAUDE_PLUGIN_ROOT}/scripts/ops-gsd-registry-sync.sh # Show registry contents cat ${OPS_DATA_DIR}/registry.json # Show health summary cat ${OPS_DATA_DIR}/cache/projects_health.json ``` ## Data flow ``` $HOME (walked recursively, depth <= OPS_GSD_SCAN_DEPTH, default 5) + any extra roots listed in OPS_GSD_SCAN_ROOTS (colon-separated) │ ▼ <any-dir>/.planning/ │ ├── HANDOFF.json ← active-phase projects ├── STATE.md ├── ROADMAP.md └── MILESTONES.md │ ▼ ops-gsd-registry-sync.sh (daemon: 6am + 6pm) │ ▼ ${OPS_D...