3 Commits

Author	SHA1	Message	Date
Molecule AI Dev Engineer A (Kimi)	eaf58bb8d4	style(tests): fix ruff F401, F541, F841, E741 in 10 files ... Cleans up 22 ruff lint errors discovered by `ruff check --select=E,W,F`: - F401 unused imports: json, sys, mock, textwrap (8 test files) - F541 f-strings without placeholders: check_migration_collisions.py - F841 unused variables: e, posted, old_title, per_context_iterated_for - E741 ambiguous variable name `l` → `ln` in test_main_red_watchdog.py All changes are test/script only; no production code affected. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-25 01:51:11 +00:00
Molecule AI Dev Engineer A (Kimi)	6ba9424196	docs(local-e2e): reference runtime PR #46 for canary mode source ... The canary short-circuit was moved from molecule-core/workspace/ (deleted in main via 9aa47643) to molecule-ai-workspace-runtime (molecule_runtime/a2a_executor.py). Update docker-compose comment so engineers can find the live code. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-23 11:41:16 +00:00
claude-ceo-assistant	59d699b61c	feat(local-e2e): session-continuity canary harness (task #342, RFC#600 gate) ... Adds a self-contained docker-compose harness in local-e2e/ that gates RFC#600-class template changes BEFORE customer canary. Implements the 4 canonical canaries: 1. 2-turn name continuity — SessionStore key derivation 2. File-only message — no caption drop-to-empty-prompt regress 3. File + prompt (multimodal) — multimodal happy path 4. Cross-session memory — explicit memory tool, distinct context_ids Architecture is deliberately lean per CTO "separate CI as possible": local-e2e/ docker-compose.yml # runtime + cp_sim ONLY (no platform Go, no pg) cp_sim/ # ~250 LoC Python A2A wire-shape emitter cp_sim/canary/ # 4 canary scenarios + layer-isolation probes scripts/run-canary.sh # one-shot orchestration (target <3 min) scripts/onboard-template.sh # gitops helper for cascade templates/session-continuity-e2e.yml # canonical workflow shim Rationale for a Python tenant-CP simulator (not the real workspace-server): SessionStore behaviour is fully owned by workspace/a2a_executor.py + executor_helpers.py — the Go platform service doesn't touch session continuity. Excising it gets the harness to <3 min cold-boot on docker-host runners and keeps the surface small enough to debug fast. The simulator emits the byte-identical JSON-RPC message/send envelope that workspace-server POSTs (cross-checked against tests/e2e/test_chat_attachments_e2e.sh and workspace/a2a_executor.py :_core_execute). Per feedback_no_single_source_of_truth: the harness IS the canonical session-continuity validator across templates. Per-template unit tests keep covering their own guard logic. Per feedback_image_promote_is_not_user_live + feedback_verify_actual_ endstate_not_ack_follow_sop: every canary asserts at the running- container layer; artifacts dump SessionStore state + runtime logs on failure for post-mortem. Rollout (deliberate sequencing, per task #342): 1. THIS PR — lands harness in molecule-core. NOT yet wired to any template repo. 2. Companion PR in molecule-ai-workspace-template-hermes — adds .gitea/workflows/session-continuity-e2e.yml. NOT required yet. 3. Bake on hermes for ≥5 business days. 4. Cascade to remaining 6 templates via onboard-template.sh. 5. Per-template BP flip — add "session-continuity-e2e (pull_request)" to status_check_contexts on each repo, hermes first. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-20 02:39:30 -07:00