Repository navigation
runtime: qualify omitted native Claude profiles with fresh exact cases #162
Description
Activity
Keep this as a capability qualification tracker. Current routing intentionally admits only Claude intent; successful shared transport execution does not enable the other profiles. The historical attempts are consumed evidence, not a reason to revive strict profile schemas or pseudo-tool/modelUsage checks. No route is enabled and no provider failure is inferred by this reconciliation.
Fresh qualification preparation and access result (2026-09-08 UTC):
- The current signed runtime 5.0.7 admits Claude only for document intent. Its public dispatcher uses normal native invocation; the historical strict adapter/schema-cycle requirements in this issue are not the current qualification path.
- Prepared three genuinely fresh synthetic corpora and separate offline rubrics for conceptual architecture, extraction, and reasoning. All remain unconsumed. Historical cases were neither replayed nor relabelled.
- An independent design review approved a one-shot admitted-intent access screen before source/build work. Full admission would require each proposed action at all three quality profiles, with matched incumbent comparisons and exact staged source/runtime binding.
- Fresh consumed access request:
05aa38a6-4840-436c-b1da-0f99c5ce274e, one attempt, zero replays, explicit Claude target, standard quality/effort, manifest SHA-256a11571908933c48fc301838d1cdb5d5f71433924af5b4b8419fd7b658695f440. - Native response: “Your organization has disabled Claude subscription access for Claude Code”. No semantic answer was returned; native return code 1, cleanup confirmed, reported input/output tokens 0. The coordinator preserved that content separately from attempt diagnostics.
No omitted profile is qualified and the public graph is unchanged. The remaining dependency is restoration of Claude Code subscription access through the intended existing account. No billing change, credential migration, API-key fallback, provider switch, or replay was performed. This issue remains open. The separate #203 content correction continues independently.
Summary
Native Claude qualification for the PR #3041 implementation admitted only
context.documents.intent. The exactarchitecture.conceptual,context.documents.extract, andcontext.documents.reasoncases were consumed once and omitted from the compiled graph without replay.Evidence and disposition
context.documents.reason: setup failed before provider start because the shared supervisor rejected the required empty non-executable value in--tools "". The supervisor now accepts empty later argv values while retaining a nonempty executable requirement, but this consumed case remains unqualified.architecture.conceptual: one provider process completed with a structured terminal presentation that the pre-amendment adapter rejected asexecution_contract_violation. The case was consumed and remains unqualified.context.documents.extract: one provider process returned a closed successful stream. Offline diagnosis showed the current CLI uses a reservedStructuredOutputpseudo-tool, reports inert installed-plugin/built-in-agent catalogs, and may list the initialized primary plus an internal helper under terminalmodelUsage. The adapter now accepts only that exact closed schema cycle and additive identity form while rejecting every external or mismatched tool. The consumed case remains unqualified.context.documents.intent: a distinct exact source-head call succeeded with one provider process, two complete document reads, two reported turns, matched primary-model identity, confirmed cleanup, and no external tool/MCP activity. A reviewed matched rubric passed against the successful Grok incumbent; Gemini produced only advisory/unknown evidence.No failed or unavailable request was replayed. Private evidence retains create-exclusive consumed markers, result digests, and bounded raw-stream digests; source contents are not attached here.
Follow-up acceptance
Define a fresh, distinct per-profile corpus and request identity before any future qualification. Admit a profile only after its own one-shot source-head canary and matched offline quality rubric pass on the exact adapter/runtime bytes. Do not reactivate these profiles as shadow routes, infer qualification from the shared transport, or reuse the consumed requests.
This issue tracks capability follow-up only; it does not block the intent-only release.