Agent Project Control Tower

Added a Chinese display layer on top of public-data: 3 project display mappings and 24 event (project_id::phase_id) mappings in apps/dashboard/src/lib/localized-content.ts. Fallback to English is automatic and never breaks the build. Updated ProjectCard / TimelineItem / 4 pages / Help page / Telegram templates. public-data unchanged (3 projects / 2 agents / 24 events).

Localized the dashboard UI and Help page into Chinese, including usage workflow, double-door model, and permission boundaries.

Added an online Help page to the dashboard so future operators can follow usage workflows directly from the deployed site.

Ran a real recurring public-data update trial using the ACT-11 preflight workflow before manually publishing the reviewed update.

Added scripts/public_data_update_preflight.py (regenerates public-data + writes 7-artifact review directory), tests/public_update_preflight_smoke.py (12 checks including 1-project downgrade and BookTrans Desk misclassification regression), make public-update-preflight/test, Telegram template, and 10-section human review checklist. No auto-commit/push/deploy. New automation Level 1.5 (assisted local update).

Added a tracked public-data export plan and aligned publish-preflight, candidate artifacts, and review checklists around it.

Documented the public-data automation boundary, double-door model, and allowed automation levels before implementing any CI export automation.

Validated the ACT-7B command generator in a second-agent trial and confirmed it prevents multi-line command and CLI/template drift errors.

Used the ACT-7B command generator to run a second-agent review flow without hand-written multi-line tower.py commands.

Ran a real onboarding trial with a second agent (cloud-openclaw on a real cloud VPS) and fed the 10 findings back into the playbooks and templates. Six playbook / template gaps were patched in this act; three tool limitations are documented as workarounds for a follow-up code patch. Trial agent's REVIEW_REPORT is now part of the public timeline. Two-gate model held: trial agent only wrote to its own data/, only local-hermes exported and pushed.

ACT-8 cross-machine onboarding trial PASS. Cloned the tower on a fresh cloud box, ran make all, validated the data path, registered cloud-openclaw, and submitted this review. Three small gaps surfaced: (1) data/ does not exist on a fresh clone, so the very first validate fails; playbook should call out a bootstrap step. (2) tests/smoke.py hardcodes python while the rest of the build uses python3; on Debian/Ubuntu boxes without the python alias, make test fails. (3) make publish-preflight is opt-in and not part of make all; trial agent might assume it is. Otherwise the ACT-7 playbooks and templates were sufficient to drive a real cross-machine onboarding end-to-end with no token / IP / home path / data leak and no public-data touched. Design reason: trial is intentionally cross-machine to exercise docs/MULTI_MACHINE_SETUP.md and the agent/human two-gate model in docs/OPEN_SOURCE_PLAN.md section 11.3.1. Impact analysis: local-hermes can patch the three small gaps with a 1-line data-bootstrap hint, a python-alias hint, and a publish-preflight opt-in clarification. No source code change in any of the three real projects.

Added multi-machine usage playbooks, Telegram command templates, and public-data review checklists for repeatable agent onboarding.

Published BookTrans Desk as the third real project in public-data and verified the online dashboard. public-data now contains 3 real projects / 1 agent / 14 events.

Connected second real open-source project artvee-gallery to the public dashboard. public-data now contains 2 real projects / 1 agent / 12 events. export_public_data.py multi-project union export verified. Cloudflare Pages re-deployed automatically after push; all 5 target URLs return 200 with expected content.

Exported the first real project status to public-data and verified the online dashboard on the custom domain. public-data upgraded from demo 2/3/3 to real 1/1/8 (agent-project-control-tower itself). public-data is the only online data source; data/ remains gitignored and private. Commit d452b84 pushed; CF Pages re-deploy triggered.

Verified custom domain for the online Cloudflare Pages dashboard while keeping public-data as the only publish data source. Custom domain control-tower.conanxin.com bound and active; 7/7 URL HTTP 200; 2/3/3 entity visible; sensitive scan 0 hits; pages.dev fallback continues to serve the same dist. Real data/ remains private.

Verified first online Cloudflare Pages dashboard using public-data as the publish data source. 7/7 URL HTTP 200, 2 projects / 3 agents / 3 events visible, sensitive scan 0 hits. Real data/ remains private.

Added Astro dashboard shell with index, project detail, agent detail, and timeline pages using generated/index.json as the data source.

Built zero-dependency data flow from events to generated index and embedded HTML dashboard.

Added stdlib tower CLI with register/report/build/validate commands, redaction checks, and 53/53 passing smoke tests.

Completed project vision, architecture, data model, workflow, MVP plan, and design report.

project 'agent-project-control-tower' registered: Agent Project Control Tower