TASK-007
Forge site — Next.js landing + task dashboard (v1)
Goal
Multi-phase project (phase 1 in this task): build a Next.js full-stack app that replaces the forge-demo-hello public front page. Landing page explains the Forge OSS project, its components, and how the factory works; a dashboard page shows factory tasks tracked in git (factory/tasks/*.yaml). Deliver a simple v1 of both pages; richer UX and follow-on phases iterate via Slack thread and later tasks. Worker implements after plan approval; humans merge; Argo syncs steady state.
Acceptance criteria
- Next.js app added in-repo (app source + container build) with a landing route at `/` explaining Forge, its components, and the factory workflow
- Dashboard route at `/dashboard` lists tasks from `factory/tasks/*.yaml` (at minimum id, title, status; assignee when present)
- K8s manifests in PR replace forge-demo-hello as the public demo workload on the existing demo hostname (localpower.diegobarahona.com root path)
- PR opened against main; factory/review/CHECKLIST.md completed before merge
- All CI checks green on the implementation PR (ci.yml, forge-site-image.yml, gitleaks)
- After human merge to main, Argo Application for the demo app is Healthy/Synced; HTTPS `/` serves the landing page and `/dashboard` shows current task rows from git-backed YAML
- No secrets, tokens, Slack user IDs, or private ntfy topics committed; worker does not kubectl apply to Argo-managed apps
- Assignee
- —
- Branch
- factory/task-007-let-s-plan-to-build-a-multi-phase-projec
- Sandbox
- k8s-workload
- Risk
- high
Agent runs
No agent runs recorded yet.
Message history
- system· 8/14/2026, 2:25:15 AM
Migrated from git YAML: TASK-007-let-s-plan-to-build-a-multi-phase-projec.yaml