Next tickets, Gmail re-auth, and how to extend the dashboard without rebuilding it.
Sprint 1 delivered the shell. The next work is either unblocking Gmail ingestion or improving the collectors so they read raw agent stores, not just reports.
Everything is plain files. If you want a new view, edit dashboard/index.html. If you want a new parser, edit dashboard/collector.py. If you want a new ticket, add a Markdown file under forge/issues/.
Think of it like… a workshop where the tools are already hung on the wall. You do not need to rebuild the workshop to make the next thing; you just pick up the right tool.
The issue format is intentionally simple: a Markdown file with a front-matter block containing status, priority, blocked_by, and owner. The dashboard does not parse these yet, but the convention is already established so future collectors can pick them up.
The re-auth command lives in the dashboard and in GMAIL-001.md. It targets the info@appfy-ai workspace account.
# GMAIL-001 — Gmail ingestion blocked
status: blocked
priority: P0
blocked_by: oauth-token-expiry
owner: user
All four configured OAuth tokens expired. Run the command below
for the business account before ingestion can resume.
open ~/Documents/Projects/appfy/organizer-loop-engineering/forge/issues/GMAIL-001.md
If you are ready to unblock Gmail, copy and run this command:
GOOGLE_WORKSPACE_CLI_CONFIG_DIR=/Users/acf/.config/gws-accounts/info-appfy-ai GOOGLE_WORKSPACE_CLI_KEYRING_BACKEND=file /opt/homebrew/bin/gws auth login --services gmail,calendar,drive --readonly