3 Commits

Author	SHA1	Message	Date
devops-engineer	55689e0b10	fix(post-suspension): migrate github.com/Molecule-AI refs to git.moleculesai.app (Class G #168) ... The GitHub org Molecule-AI was suspended on 2026-05-06; canonical SCM is now Gitea at https://git.moleculesai.app/molecule-ai/. Stale github.com/Molecule-AI/... URLs return 404 and break tooling that clones / pip-installs / curls them. This bundles all non-Go-module URL fixes for this repo into a single PR. Go module path references (in *.go, go.mod, go.sum) are out of scope here -- tracked separately under Task #140. Token-auth clone URLs also flip ${GITHUB_TOKEN} -> ${GITEA_TOKEN} since the GitHub token does not auth against Gitea. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 13:08:15 -07:00
Hongming Wang	dfeefb0acc	fix(workspace-server): vendor upstream derive-provider.sh + close 12-prefix drift ... The drift gate's monorepoRoot walk-up looked for workspace-configs-templates/ which is gitignored locally and doesn't exist in this repo at all (the canonical script lives in molecule-ai-workspace-template-hermes). Test failed on CI from day one with "could not find monorepo root". Two layered fixes in one PR: 1. Vendor upstream derive-provider.sh as testdata/ + drop monorepoRoot. The vendored copy has a header pointing operators at the upstream source and a one-line cp command for refresh. Test now reads two files (vendored shell + workspace_provision.go) via package-relative paths — Go test sets cwd to the package dir, so this is hermetic without any walk-up gymnastics. 2. Update the case-statement regex to match upstream's renamed variable (${_HERMES_MODEL} since v0.12.0, the resolved value of HERMES_INFERENCE_MODEL with a HERMES_DEFAULT_MODEL legacy fallback). Regex now accepts either spelling so a future rename fails loudly on the parser-sanity check rather than silently returning empty. Vendoring upstream surfaced real drift the gate was designed to catch: upstream v0.12.0 added 12 provider prefixes that deriveProviderFromModelSlug didn't handle (xai/grok, bedrock/aws, tencent/tencent-tokenhub, gmi, qwen-oauth, lmstudio/lm-studio, minimax-oauth, alibaba-coding-plan, google-gemini-cli, openai-codex, copilot-acp, copilot). Without these, Save+Restart on a workspace using one of those prefixes would persist LLM_PROVIDER="" and the next boot would fall back to derive-provider.sh's runtime *=auto branch — losing the user's explicit choice on every restart. Added all 12 case clauses + 16 new table-driven test cases (covering both canonical and aliased forms). Drift gate now passes; future upstream additions will fail loudly with a "DRIFT: ..." message pointing the engineer at the missing case. Task: #242	2026-05-02 23:51:23 -07:00
Hongming Wang	747c12e582	test(a2a): protocol-shape replay corpus gate (#2345 follow-up) ... Backward-compat replay gate for the A2A JSON-RPC protocol surface. Every PR that touches normalizeA2APayload OR bumps the a-2-a-sdk version pin runs every shape in testdata/a2a_corpus/ through the current code and asserts: valid/ — every shape MUST parse without error and produce a canonical v0.3 payload (params.message.parts list). invalid/ — every shape MUST be rejected with the documented status code and error substring. What this prevents The 2026-04-29 v0.2 → v0.3 silent-drop bug (PR #2349) shipped because the SDK bump PR didn't replay v0.2-shaped inputs against the new code; the shape-mismatch surfaced only in production when the receiver's Pydantic validator silently rejected inbound messages. This gate would have caught it pre-merge. Hand-verified: reverting the v0.2 string→parts shim in normalizeA2APayload fails 3 of the v0.2 corpus entries with the exact rejection class the production bug exhibited. Corpus contents (11 entries) valid/ (10): v0_2_string_content — basic v0.2 (the broken case) v0_2_string_content_no_message_id — v0.2 + auto-fill messageId v0_2_list_content — v0.2 with content as Part list v0_3_parts_text_only — canonical v0.3 v0_3_parts_multi_text — multi-Part list v0_3_parts_with_file — multimodal (text + file) v0_3_parts_with_context — contextId for multi-turn v0_3_streaming_method — message/stream variant v0_3_unicode_text — emoji + multi-script v0_3_long_text — 10KB text Part no_jsonrpc_envelope — bare params/method without outer envelope (legacy senders) invalid/ (3): no_content_or_parts — message has neither field content_is_integer — wrong type for v0.2 content content_is_bool — wrong type, separate from int so the failure msg identifies which type-class regressed Plus 4 inline malformed-JSON cases (truncated, not-JSON, empty, whitespace) that can't be expressed as JSON corpus entries. Coverage tests The gate has 4 test functions: 1. TestA2ACorpus_ValidShapesParse — replay valid/ corpus, assert no error + canonical v0.3 output (parts list non-empty, messageId non-empty, content field deleted). 2. TestA2ACorpus_InvalidShapesRejected — replay invalid/ corpus, assert rejection matches recorded status + error substring. 3. TestA2ACorpus_MalformedJSONRejected — inline cases for non-parseable bodies. 4. TestA2ACorpus_HasMinimumCoverage — at least one v0.2 + one v0.3 entry exists (loses neither side of the bridge). 5. TestA2ACorpus_EveryEntryHasMetadata — _comment/_added/_source on every entry per the README policy; _expect_error and _expect_status on invalid entries. Documentation testdata/a2a_corpus/README.md describes the corpus contract: - When to add entries (new SDK shape, new production-observed shape). - When NOT to add (test scaffolding, hypothetical futures). - Removal policy (breaking change, deprecation window required). Verification - All 24 corpus subtests pass on current main. - Hand-test: revert the v0.2 compat shim → 3 v0.2 entries fail the gate with the exact rejection class the production bug exhibited. Confirmed. - Whole-module go test ./... green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-30 01:26:02 -07:00