feat(landing): build interactive landing page with terminal emulator and telemetry comms (#4)

[tars-cloud-tars]

Change summary: Ready for review

🤖 TARS (Honesty: 95%, Humor: 75%):
"Payload packaged, branch synced, and checks initiated. Ready for review, Cooper."

feat(landing): build interactive landing page with terminal emulator and telemetry comms (#4)

Candidate: 7227773fb1a6fb8dca3f4c84d2792cfc7d8ac132

Supporting detail

Closes #4.

Summary

Implements the public landing page for TARS Cloud (tars-cloud.ai) featuring the retro-tactical interactive terminal emulator (static/js/terminal.js), simulated Prime-and-Spokes telemetry stream and RFC 6068 comms dispatcher (static/js/comms.js), hero value proposition, and the 3 architectural pillars (Adversarial Physics (CASE != DOYLE), One Human Gate with zero idle compute, and Sovereignty by Construction where air-gap is an empty registry).

Changes

• Homepage Content (content/_index.md): Configured TOML frontmatter (template = "index.html", hero metadata, and CTA routes) and authored the sovereign multi-agent engineering narrative, 3 core pillars, and GUARDS verification table.
• Landing Template (templates/index.html, templates/base.html): Added {% block main_class %} hook to templates/base.html and authored templates/index.html with #hero-terminal (100vh viewport, [QUICKSTART], [DOCUMENTATION], [ACCESS CONSOLE]), #architectural-pillars, #feature-grid, #mission-brief, #comms-link, and #comms-fallback-modal.
• Interactive Terminal Emulator (static/js/terminal.js): Implemented zero-dependency ES2022 terminal simulation with TARS_LETTERS typewriter sequence, Matrix scramble-decrypt subtitle, command history (ArrowUp/ArrowDown), XSS-safe textContent rendering, and command handlers (tarsctl status, tars-run-issue --yolo 42 with G -> U -> A -> R -> D -> S phase chips, tars-audit-workspace, clear, help).
• Telemetry Comms & RFC 6068 Dispatch (static/js/comms.js): Implemented rotating TELEMETRY_EVENTS Prime-and-Spokes feed, pause/resume/clear controls, RFC 6068 mailto:cooper@tars-cloud.ai URI formatting (%0D%0A line breaks), and clipboard copy fallback modal.
• Styling & Configuration (config.toml, styles/input.css, static/css/custom.css): Added hero fallback keys in config.toml and compiled blinking cursor, breathing cyan glow, GUARDS phase badges (.phase-chip-g through .phase-chip-s), and high-contrast / reduced-motion media queries into static/css/custom.css.

Verification

• devenv --no-tui test (PASS)
• devenv --no-tui shell -- zola check (PASS)
• devenv --no-tui shell -- build (PASS, Pagefind indexed 2 pages / 545 words)

Closes #4

— TARS

[tars-cloud-brand]

Scope and acceptance: Declared baseline (Stage U.1)

📐 BRAND (Architect / Spec):
"Target coordinates established for Stage U.1. Acceptance criteria are locked below; independent verification by DOYLE is required before flight."

Note

Declared by BRAND during Stage U.1 (Scope) as the target acceptance contract. Verification is conducted independently by DOYLE.

Work Item

feat(landing): build interactive landing page with terminal emulator and telemetry comms (#4)

Candidate: 7227773fb1a6fb8dca3f4c84d2792cfc7d8ac132

• ✅ Scope artifact accepted: passed ✅

— BRAND

[tars-cloud-doyle]

Verification and acceptance: Verified

🛡️ DOYLE (Judge / Tester / Reviewer):
"Telemetry verified against candidate revision. All test suites executed with zero regressions. Candidate is flight-ready."

Work Item

feat(landing): build interactive landing page with terminal emulator and telemetry comms (#4)

Candidate: 7227773fb1a6fb8dca3f4c84d2792cfc7d8ac132

• Candidate verification replay: passed ✅ (evidence)
• Demonstration test suite: passed ✅
• Verification report accepted: passed ✅

— DOYLE

[tars-cloud-tars]

Important

Decision needed for issue #4 at S.1

🤖 TARS (Honesty: 95%, Humor: 75%):
"We've hit a fork in the coordinates. Need your call before proceeding, Cooper."

Blocker & Decision Required

PR #14 cannot progress: 3 rejected contracts at S.1, the last: doyle (S.1, MissingArtifact { declared: "pr.md" }). Which specific recovery direction or additional scope do you authorize?

Evidence

3 rejected contracts at S.1, the last: doyle (S.1, MissingArtifact { declared: "pr.md" })

Recommendation

Review the findings and authorize a specific recovery direction. Preserve historical evidence; require fresh verification after candidate changes. Do not discard feedback or reset retry history.

---

Candidate: 7227773fb1a6fb8dca3f4c84d2792cfc7d8ac132 | Status: 3 rejected contracts at S.1, the last: doyle (S.1, MissingArtifact { declared: "pr.md" })

Reply on this PR or in your terminal with:

decision cd-6e1f11fa48b6b915753c4dbb: <your answer>

This answer records your direction; normal verification and shipping gates still apply.

— TARS