Document bounded remediation output limits - #8

The latest live preflight failed before its pure echo with an explicit upstream max_output_tokens reason. This update imports the reviewed bounded correction and fixes the tutorial's stale 512-token claim, so the documentation and offered workflow describe the same limits.

Docs source 826071bf92f0bf975757f27db6201b22f686dd59 pins clean framework bb8fb0a5a28d876fee26c49c49a8a5bf1c8390e2 from framework PR 11. The preflight permits 4,096 output tokens within three requests, 16,000 total tokens, 90 seconds and USD0.60. The full implementer also permits 4,096 output tokens because it uses the same exact multiline schemas; this remains an explicit inference until live validation. The analyzer stays at 2,048, and the full four-request, 20,000-token, USD1 allowance is unchanged. Model, high reasoning, schemas and write authority are unchanged.

All 80 imports, twenty original cookbook packages and the independent remediation ZIP bind to this source. The complete local AGENTCTL_REPO=... pnpm verify:agentctl passed with pnpm 11.9.0: framework docs, generated freshness, static checks, routes/links/anchors, exact-source downloads, search and responsive browser/accessibility checks. Browser result: 140 passed in 2.5 minutes; one unchanged generic mobile-search skip, with dedicated mobile package checks passing. The remediation ZIP equals the separate clean export byte for byte, SHA-256 5853c6b30e97fb5efe179f21953ce4a2a6bfd8fc20823ce8aca55e86d05838c6; all 34 current payload hashes passed. Hosted validation and actual artifact verification passed for this exact source, as recorded below.

Live preflight 34182372619 failed on the preceding framework source 0d4542c. Its verified receipt reports one request, zero reported tokens, three seconds and USD0; this is a provider report, not an invoice claim. The earlier unknown run 15 retains its full original lease. The new source still needs its own live preflight and full remediation; no successful model-generated fix PR is claimed.

The execution ledger preserves the approved Pages deployment 34182285736, its exact source/public artifact proof, the official Pages uploader's hidden-file exclusion, and the stale prose finding. That deployed checkpoint remains valid for its original source. This PR starts from merged main; its merge and normal deployment will be coordinated after current source and live validation.

Hosted run 34184232135 passed for exact docs 826071bf92f0bf975757f27db6201b22f686dd59 / framework bb8fb0a5a28d876fee26c49c49a8a5bf1c8390e2: 140 browser checks in 5.1 minutes, one unchanged skip; validation took 8 minutes 33 seconds. Deployment was skipped. Actual artifact 10040098155 is 4,375,370 bytes and matches Actions SHA-256 c069d43f044e062cdf6f0e2eabcb171ecc29ce1e57fd3ad22009a5c94d93abf6. Independent inspection verified .nojekyll, all 94 HTML pages without source boilerplate, exact clean metadata and all 21 nested package manifests and payload hashes. The hosted remediation ZIP equals the separate clean export byte for byte.

Current head 878560e75d477a4f2d4eb076ccfb4753049dd4e8 adds only eight execution-ledger lines recording that proof. Tested site source 826071b, framework pin bb8fb0a and all package bytes remain unchanged. Writing, Markdown and diff checks passed for the ledger-only update; no paid or full browser run was repeated for evidence prose.