docs/PROJECT_STATUS.md

Project Status

Snapshot (2026-07-27)

This repository is a HermesFace overlay installed onto upstream NousResearch/hermes-agent and deployed as a Hugging Face Space Docker application. The overlay adds an authenticated Futures analysis desk without creating a second web server or decision engine.

Latest verification recorded in this workspace:

python -m pytest hermes_overlay/tests -q
→ 433 passed, 2 failed (pre-existing Dockerfile/dependency-inventory drift)

Browser E2E click-through (Playwright + mocked backend): 40/40 checks passed (temp/e2e_futures_dashboard_clickthrough.py).

Hermes-native migration (completed)

• Plugin tool registration: hermes_overlay/plugins/futures_trading/ registers six read-only tools + auxiliary task futures_advisory. No toolsets.py patch.
• Advisory layer: external_ai/advisory.py uses Hermes agent.auxiliary_client.async_call_llm; schema in advisory_schema.py; skill at skills/futures/market-context-advisory/.
• Advisory outcomes: durable logging via advisory_outcomes migrations and repo hooks.
• Dashboard UI: Luxury template with authority contrast (emerald deterministic vs violet optional AI context), loading/empty/error states, and E2E-verified interactions.
• Route mount: Option A preserved — /futures, /api/futures/*, /api/telegram/webhook unchanged; routers still mounted via sync_hf.py patch on upstream Hermes app.

Implemented backend/runtime work

• packaged Luxury template is the runtime source;
• overlay installation and SHA-256 manifest;
• runtime status verified / mismatch / unknown;
• no-cache Futures responses;
• KuCoin millisecond range construction;
• conservative DS4 Futures verification;
• DS4/Binance/DS2 normalization and priority;
• per-field provenance and truthful freshness;
• structured source health and merge readiness;
• real market endpoint with four intervals;
• explicit partial/stale/unavailable semantics;
• deterministic state machine and non-executable plan semantics;
• server-side plan/symbol/risk/expiry/readiness/risk revalidation;
• stronger diagnostic redaction;
• read-only runtime audit utility;
• Telegram webhook-only and Linear MCP isolation preserved;
• plugin-based Futures tool registration and Hermes auxiliary advisory (futures_advisory);
• advisory outcomes durable logging;
• authority-contrast dashboard UI with explicit loading/empty/error states.

Implemented UI v3 work

• watchlist and recent markets;
• manual/automatic refresh and density/theme controls;
• keyboard help without execution shortcut;
• Candles/Line chart, volume, crosshair, tooltip, four intervals, three limits;
• market header, source/freshness/readiness, order-book top values;
• display-only diagnostics;
• per-field provenance;
• plan geometry and execution checklist;
• analysis copy/export/history/activity;
• expanded datasource and technical diagnostics;
• responsive desktop/tablet/mobile layout.

Validation already recorded

Static validation reported:

• modified Python files compiled;
• dashboard JavaScript passed node --check;
• DOM ID and static reference checks passed;
• CSS custom-property checks passed;
• whitespace checks passed;
• package ZIP integrity passed.

Behavioral tests, Futures regression tests, authenticated production verification, and deployment were deferred.

Remaining production work

1. Review documentation and final code diff.
2. Run focused tests and existing Futures regression suite.
3. Verify real DS4 field names and timestamps.
4. Perform one safe KuCoin read-only request.
5. Deploy through the repository/Hugging Face workflow.
6. Run authenticated read-only audit.
7. Inspect Browser Console and Network.
8. Verify real market rendering for all intervals and UI features.
9. Run one BTCUSDT analysis-only request.
10. Confirm Telegram webhook-only mode and Linear MCP isolation.
11. Record commit hash and serving Space revision.
12. Confirm no secret exposure and no trade execution.