Restore complete selected Z.ai source acquisition and assess D-082 evidence #43

New issue

Closed

opened 2026-10-27 08:26:29 +00:00 by kilo · 1 comment

kilo commented

2026-10-27 08:26:29 +00:00

Member

Owner-authorized scope

This issue registers the explicitly authorized follow-up to the completed MI #15 producer and MI #19 installed acceptance. Restore reliable complete publication of the existing selected eight-source Z.ai/models.dev generation and assess only genuinely applicable evidence against the exact integrated Router D-082 implementation. This does not authorize Router changes, production activation, live inference, release/deployment, or product GO.

Evidence and first defect

At MI develop 8f572c332db8290b5dad9e03f5b0f960271a8349, zai.SOURCES declares pricing at https://docs.z.ai/guides/overview/pricing.md with a 2,620-byte limit. Router #222 comment 19056 reports seven successful inputs, pricing failing its bound, then a separate bounded diagnostic request receiving HTTP 500; independently rendered documentation text exceeded 2,620 bytes, but that was not a raw HTTP-body measurement. acquisition.fetch() reads max_bytes + 1, compares that bounded read with Content-Length, and only then constructs Capture, potentially misclassifying a complete oversized response as incomplete framing.

Acceptance

Reproduce bounded live source behavior without redirects, arbitrary retries, unlimited reads, publication activation, or logging/redistributing official page contents. Record status, safe headers, exact raw body length/digest/encoding and retrieval time when obtainable. Distinguish complete oversized responses from truncated framing and transient failures.
Correct the fetch classification if reproduced. Preserve strict rejection and useful diagnostics for genuinely incomplete/inconsistent HTTP framing, timeout, non-success status, compression and interrupted transfer.
If the current pricing document has grown and remains structurally compatible, select a justified bounded policy from measured evidence. Inspect old/new SOURCES, SOURCE_CONFIG and SCOPE fingerprints and preserve /1 and /2, retained references/history and existing-store refusal semantics. Never rewrite or relabel old publications; use a separately identified compatible lifecycle or fresh publication store when required. Do not make the fingerprint artificially stable.
Exercise the actual supported eight-source acquisition, normalize, and producer.publish path with complete validated inputs where public sources permit. Verify all-eight completeness, atomic activation, history and prior-active-pointer preservation on failure. Report exact remaining public-source failures without claiming an incomplete run succeeded.
Assess actual source facts against Router D-082 at its exact current reviewed implementation. Never infer positive channel, configuration, effort, physical identity, freshness, unit/basis or input allowance. Report REAL_SOURCE_POSITIVE_ADOPTION = NOT_ESTABLISHED if no fact satisfies all accepted conditions; do not modify Router or weaken admission.
Add deterministic original-fixture regressions for framing/size classification, pricing-table structure/basis, scope compatibility and refresh atomicity as relevant. Preserve all existing publication and temporal contracts.
Run focused checks, make check, and applicable packaging/installed and exact-pin Router compatibility checks. Obtain fresh independent whole-PR review and integrate only under the explicit loop's exact currentness and acceptance gates.

Boundaries

One existing source adapter and publication mechanism only. No crawler, new source family, scheduler, new schema version, new acquisition pipeline, private account data, invented positive Router facts or foreign repository mutations. SOURCE_CONFIG is deliberately derived from repr(SOURCES); policy changes can change producer scope and must not bypass consumer review.

Refs #15 #19

## Owner-authorized scope This issue registers the explicitly authorized follow-up to the completed MI #15 producer and MI #19 installed acceptance. Restore reliable complete publication of the existing selected eight-source Z.ai/models.dev generation and assess only genuinely applicable evidence against the exact integrated Router D-082 implementation. This does not authorize Router changes, production activation, live inference, release/deployment, or product GO. ## Evidence and first defect At MI develop `8f572c332db8290b5dad9e03f5b0f960271a8349`, `zai.SOURCES` declares pricing at `https://docs.z.ai/guides/overview/pricing.md` with a 2,620-byte limit. Router #222 comment 19056 reports seven successful inputs, pricing failing its bound, then a separate bounded diagnostic request receiving HTTP 500; independently rendered documentation text exceeded 2,620 bytes, but that was not a raw HTTP-body measurement. `acquisition.fetch()` reads `max_bytes + 1`, compares that bounded read with `Content-Length`, and only then constructs `Capture`, potentially misclassifying a complete oversized response as incomplete framing. ## Acceptance - Reproduce bounded live source behavior without redirects, arbitrary retries, unlimited reads, publication activation, or logging/redistributing official page contents. Record status, safe headers, exact raw body length/digest/encoding and retrieval time when obtainable. Distinguish complete oversized responses from truncated framing and transient failures. - Correct the fetch classification if reproduced. Preserve strict rejection and useful diagnostics for genuinely incomplete/inconsistent HTTP framing, timeout, non-success status, compression and interrupted transfer. - If the current pricing document has grown and remains structurally compatible, select a justified bounded policy from measured evidence. Inspect old/new `SOURCES`, `SOURCE_CONFIG` and `SCOPE` fingerprints and preserve `/1` and `/2`, retained references/history and existing-store refusal semantics. Never rewrite or relabel old publications; use a separately identified compatible lifecycle or fresh publication store when required. Do not make the fingerprint artificially stable. - Exercise the actual supported eight-source acquisition, `normalize`, and `producer.publish` path with complete validated inputs where public sources permit. Verify all-eight completeness, atomic activation, history and prior-active-pointer preservation on failure. Report exact remaining public-source failures without claiming an incomplete run succeeded. - Assess actual source facts against Router D-082 at its exact current reviewed implementation. Never infer positive channel, configuration, effort, physical identity, freshness, unit/basis or input allowance. Report `REAL_SOURCE_POSITIVE_ADOPTION = NOT_ESTABLISHED` if no fact satisfies all accepted conditions; do not modify Router or weaken admission. - Add deterministic original-fixture regressions for framing/size classification, pricing-table structure/basis, scope compatibility and refresh atomicity as relevant. Preserve all existing publication and temporal contracts. - Run focused checks, `make check`, and applicable packaging/installed and exact-pin Router compatibility checks. Obtain fresh independent whole-PR review and integrate only under the explicit loop's exact currentness and acceptance gates. ## Boundaries One existing source adapter and publication mechanism only. No crawler, new source family, scheduler, new schema version, new acquisition pipeline, private account data, invented positive Router facts or foreign repository mutations. `SOURCE_CONFIG` is deliberately derived from `repr(SOURCES)`; policy changes can change producer scope and must not bypass consumer review. Refs #15 #19

kilo referenced this issue

2026-10-27 08:36:57 +00:00

Restore complete Z.ai source acquisition #44

kilo commented

2026-10-27 08:48:32 +00:00

Author

Member

Completion evidence

PR #44 merged to develop at 756a45cdaeee15c9d4c231fd2bf95287c74b5609; the merged PR head aff276cb7db98544419780f4fc631a719a86be94 is an ancestor of current develop. The exact approved base was 8f572c332db8290b5dad9e03f5b0f960271a8349.

The authorized pricing URL returned HTTP 200 at 2026-10-27T08:28:07Z. A bounded 65,536-byte read (no redirects/proxy, identity encoding) reached EOF at 3,010 bytes, UTF-8, SHA-256 33a372c40dc41ea671512a575590cdd218e648897e4b4dce9caa49fc7dc0e205; Content-Length was absent. This exceeded the old 2,620-byte cap. The merged 4,096-byte cap gives bounded headroom and intentionally changes the existing source-config/scope fingerprint; it does not change /1 or /2 payload schemas.

A complete real-source run at 2026-10-27T08:31:19Z fetched and normalized all eight inputs, then published in a fresh disposable store. The active reference matched the returned publication reference: 10f30c51433244e02c2abd2186a41aa98c169478bc47d8cbf829f0af6f05d25f; status phase was complete and its last-success timestamp matched. The cut contained 32 observations, 29 claims and 2 uncertain campaigns. Old-scope storage remains immutable and rejects the new scope; only a fresh store accepted the changed fingerprint. The official page body was not retained or redistributed.

An independent reviewer at the exact PR head parsed the live response through the selected # Pricing / Latest Models parser: USD per 1M tokens; GLM-5.3-Flash input $0.15, cached input $0.03, output $0.50; cached storage Limited-time Free. This temporary offer is not a permission or entitlement to route an account.

REAL_SOURCE_POSITIVE_ADOPTION = NOT_ESTABLISHED. Current source scope has no serving channel; source facts do not establish exact per-subject reasoning configuration/effort or positive freshness; the current Router D-082 consumer remains pinned to the previous MI scope. No Router change, production activation, live inference or product GO was performed.

Validation: focused acquisition 6/6 and Z.ai source 19/19; make check passed (181 tests, Ruff, formatting, basedpyright and diff checks); uv build and isolated installed distribution compatibility passed for current/direct/rebuilt and legacy/current/producer/downgrade modes. Independent whole-PR review: exact-head APPROVE, no findings.

## Completion evidence PR #44 merged to `develop` at `756a45cdaeee15c9d4c231fd2bf95287c74b5609`; the merged PR head `aff276cb7db98544419780f4fc631a719a86be94` is an ancestor of current develop. The exact approved base was `8f572c332db8290b5dad9e03f5b0f960271a8349`. The authorized pricing URL returned HTTP 200 at 2026-10-27T08:28:07Z. A bounded 65,536-byte read (no redirects/proxy, identity encoding) reached EOF at 3,010 bytes, UTF-8, SHA-256 `33a372c40dc41ea671512a575590cdd218e648897e4b4dce9caa49fc7dc0e205`; `Content-Length` was absent. This exceeded the old 2,620-byte cap. The merged 4,096-byte cap gives bounded headroom and intentionally changes the existing source-config/scope fingerprint; it does not change `/1` or `/2` payload schemas. A complete real-source run at 2026-10-27T08:31:19Z fetched and normalized all eight inputs, then published in a fresh disposable store. The active reference matched the returned publication reference: `10f30c51433244e02c2abd2186a41aa98c169478bc47d8cbf829f0af6f05d25f`; status phase was `complete` and its last-success timestamp matched. The cut contained 32 observations, 29 claims and 2 uncertain campaigns. Old-scope storage remains immutable and rejects the new scope; only a fresh store accepted the changed fingerprint. The official page body was not retained or redistributed. An independent reviewer at the exact PR head parsed the live response through the selected `# Pricing` / `Latest Models` parser: USD per 1M tokens; GLM-5.3-Flash input `$0.15`, cached input `$0.03`, output `$0.50`; cached storage `Limited-time Free`. This temporary offer is not a permission or entitlement to route an account. `REAL_SOURCE_POSITIVE_ADOPTION = NOT_ESTABLISHED`. Current source scope has no serving channel; source facts do not establish exact per-subject reasoning configuration/effort or positive freshness; the current Router D-082 consumer remains pinned to the previous MI scope. No Router change, production activation, live inference or product GO was performed. Validation: focused acquisition 6/6 and Z.ai source 19/19; `make check` passed (181 tests, Ruff, formatting, basedpyright and diff checks); `uv build` and isolated installed distribution compatibility passed for current/direct/rebuilt and legacy/current/producer/downgrade modes. Independent whole-PR review: exact-head APPROVE, no findings.

kilo closed this issue

2026-10-27 08:48:38 +00:00