Publication: AppForge v1.0.0 — rename, badges, canonical status doc

[adbarc92]

Publication prep (the original mission), now that the engine is complete. This PR now carries the full v1.0 release, not just the README rewrite.

Stacked on #8 (final engine PR) so the README describes the merged system. Merge order: #7 → #8 → this.

1. Evidence-based README + MIT LICENSE (original scope)

• README rewritten to describe the real architecture — MCP state server, six-phase dependency graph, independent worker processes, approval gates, budget auto-downgrade, live web UI — evidence-forward: every headline claim links to a real, existing test, plus the committed documented run (docs/runs/2026-07-24/).
• LICENSE added (MIT, © Alex Barclay) — the repo declared MIT but had no file.
• Repo description + topics set on GitHub (mcp / model-context-protocol / multi-agent / orchestration / …).

2. Rename DevTeam.AI → AppForge

The project has been AppForge since the engine rewrite, but the package metadata, prompts, config comments, and UI still said DevTeam.AI.

• pyproject: name devteam-ai → appforge, placeholder your-repo URLs → the real repository, authors → AppForge Contributors
• prompts, config/*.yaml, agents, tests, CI, phase briefs, frontend/src/App.tsx
• DEVTEAM_PHASE → APPFORGE_PHASE; page title frontend → AppForge
• uv.lock regenerated

docs/superpowers/{plans,specs} are deliberately left untouched — they are dated design records that quote code verbatim, so rewriting them would falsify history.

3. Version 1.0.0

• pyproject 0.1.0 → 1.0.0, classifier 3 - Alpha → 5 - Production/Stable
• frontend/package.json 0.0.0 → 1.0.0 (backend/main.py already declared 1.0.0)
• tagged v1.0.0

4. Status doc + README polish

• docs/STATUS.md — new canonical, living status doc (state summary + newest-first session log). Supersedes the dated Status-*.md snapshots, which still described the retired LangGraph orchestrator.
• Badges — CI, version, tests, coverage, Python, license.
• Configuration table for the env vars actually read by backend/config.py, and a CLI flag table for run.py — neither was documented.
• Architecture diagram rebuilt. Its box borders were 41/42/43 characters on three different lines and the worker stems did not line up; all stems now align at columns 15/29/43. The entry point now shows the invocation that actually works (python -m backend.engine.run) instead of the appforge console script, which is declared in pyproject but not installed (the project has no [build-system]).
• CLAUDE.md — replaced the stale "Active session pickup" block, which pointed new sessions at Status-2026_06_02.md and Phase 6 work that the engine rewrite made moot; LangGraph-era sections now flagged as historical.

Verification

Check	Result
uv run pytest tests/	154 passed, 86.93% coverage (gate 70%)
cd frontend && npm test	28 passed across 6 files
uv run ruff check backend/ tests/	clean
uv run black --check backend/ tests/	clean, 66 files
cd frontend && npm run build	succeeds
README links	all 9 relative links resolve; #tests anchor valid

Known follow-ups (not in this PR)

• [project.scripts] appforge is declared but never installed — the project has no [build-system], so uv sync skips entry points. Either add one or drop the declaration.
• ENABLE_PHASE4 is now dead config: backend/config.py reads it and tests/unit/test_config.py tests its default, but nothing consumes it (same shape as the SQLITE_PATH config dropped in cde5ab7).
• pyproject still depends on langchain* and lists crewai in keywords/mypy overrides, left over from the retired orchestrator.