Repository navigation
Description
Parent workstream: #320
Epic: #318
Priority: P2 · Audit findings: API-DOC-07
Current verified outcome — October21,2026
Documentation acceptance complete; close this ticket.
A reader asking for 90 days or a year of catalog streams now sees the 1–366-day limit, 90-day example, exclusive periods and coverage caveats in normal HTML, Markdown and full AI text on both hosts. The separate playcount maximum remains 31 days. The matching Releases spec is current.
All four range criteria are satisfied. #201's source and regression test are included exactly in actual #207; #201 was closed as contained without merging it again or deleting its branch. No new history collection, provider query or guarantee of complete 366-day data is claimed.
Release chain: API #1068 pagination repair → API #1067, actual db3cdd16c7225d2090ca74a1a06df8914c6fc379 → Marketing #207, actual 5477f219ebd9b59fdd009dbd1b3f539dfc292f73 → Docs #389, actual fcf892986998076284d7c4407ca538be9e69d4a7.
The retained public source pin names that actual Marketing merge and matches all 239 managed source hashes plus navigation. Selected normal HTML/Markdown, four complete spec objects and full AI text match the released content. Publication was checked without credentials, cache busting, host overrides or retries. No real account, payment, provider, site-lifecycle or customer operation was performed. Earlier dated global CLI/hosting notes below are historical; their unrelated gates are not silently transferred into this ticket's narrower acceptance.
Original audit problem
GET /api/catalogs/{catalogId}/streams is documented with maximum 31 days while the audited validator and MCP tool support 1–366. Generated clients or forms may reject valid longer comparisons. The separate Spotify playcount endpoint intentionally retains its 31-day limit.
Scope and ownership
- Update only catalog stream-history days constraints and examples.
- Preserve the distinct Spotify playcount limit and existing completeness/provenance caveats.
- Document paging/performance considerations without implying historical data was backfilled.
- Propagate the corrected contract to both public documentation surfaces under the maintained-source workflow.
Planning is tracked in Mono. Implementation and release PRs belong in the owning repositories under their current branch rules.
Acceptance criteria
- Stream-history schema accepts 1 and 366 and rejects 0 and 367, matching the released validator.
- The independent playcount contract still rejects values above 31.
- A 90-day or year-long example is present with accurate coverage caveats.
- Rendered forms/spec downloads and LLM discovery show the corrected bound after publication.
Evidence and existing work
Baseline: October 10, 2026 audit of July 10–October 10 merges. Recheck current source and existing tracker comments before implementation. Source findings do not establish authenticated production behavior.
Related existing work:
- https://github.com/recoupable/docs/pull/354
- Support year-long saved catalog stream comparisons api#997
Continue or reconcile the linked implementation work; this ticket owns the stated audit correction and does not replace the original feature tracker.
Source corrections released — October 12, 2026
The streams history parameter now accepts 1–366 days with a 90-day example and coverage/paging caveats. The separate playcount limit stays 31. The contract guard compares the accepted maximum and maximum+1 against the actual validator. Published forms/spec/LLM readback remains a release gate.
All five approved source PRs are merged: API #1032, Marketing #152, Docs #373, CLI #26, and App #2242. Mono #373 records the five source references at e650245fe3267a08b94abbb75dc30a8a4108c020. The immutable provenance chain is API 0a590490c0e005045e4cbf399fe552dc41e6b9a3 → Marketing 62cc352c4c90d4578bea4352001fc459b7566e1b → Docs fa6dc9e761056066299dde4525552b0d14442f1f. App source is d13bdcb7b112ff0ed8d9d243ae7c6fd56f9a80d4; CLI source is a11bff0a36e339e94ad6921e55d82ec9472d0e35.
Verified publication: API, App and Marketing main checks pass and their canonical Vercel aliases are READY at those actual merge commits. All 231 merged Docs files/navigation match Marketing. Five representative Markdown pages pass on both public hosts; all 12 downloadable split specs on both hosts exactly match source. Canonical Marketing human pages and both LLM catalogs pass. Both human catalog pages show the 1–366 range; the separate playcount maximum remains 31.
Remaining release gates: CLI build/typecheck/77 tests passed, but npm publication failed with HTTP 404; the registry still serves 0.1.15. The release bot bumped source to 0.1.16 without publishing it. A valid NPM_TOKEN replacement and installed-registry-package verification are required; no token value belongs in an issue. Retained-host normal /llms-full.txt still returns cached v0.1.13/--room-id guidance (cf-cache-status: HIT, max-age=86400); a cache-busted read shows the corrected CLI/Context/Sites content. Its human /mcp still returns 405. Docs main's Mintlify deployment succeeds, but these URL/cache problems are not thereby resolved. Mintlify connection/routing repair and host cutover remain explicitly deferred. No hosted Context, media, OAuth/client, or unresolved-feature acceptance is inferred from this source release.
Ticket acceptance update: First three range criteria are verified by actual validator fixtures and published source/examples. Canonical LLM content is current; retained aggregate discovery/cache compatibility remains tracked with #337 before complete dual-host acceptance.
Range publication narrowed — October 20, 2026
Normal public readback at 14:13 UTC verifies both sites' HTML, direct/raw Markdown and downloadable Releases specification show the accepted 1–366-day stream range, the 90-day example, coverage caveats and separate 31-day playcount maximum. Both served stream operations exactly match released Marketing 872337ab. Canonical full AI text also includes the bound. Seven of eight checked responses meet this range-specific criterion; no authenticated catalog/provider request or manual hosting change occurred.
The retained site's normal full AI text includes the current operation description but omits parameter details, including the numeric bound. This is a content-format omission; absence of 366 does not establish stale publication. The maintained api-reference/songs/catalog-streams.mdx contains only title/operation frontmatter. The next concrete source correction is explicit range/coverage prose in that maintained page, followed by normal automatic publication and aggregate-text readback. Hosting repair is not required to prepare that correction, and no cache bypass/purge was used. Keep the final publication criterion open.
Receipt: .local/audits/recoup-reconciliation-2026-10-10/catalog-range-readback-20261020T141331Z/readback.json. An earlier Python certificate-store failure is preserved separately; successful reads used curl with normal TLS verification, not disabled verification. This checks documentation, not completeness of actual catalog measurements.
Omitted AI-text limits corrected in source — pending review/release
Marketing #201, exact 12a16702b9749d9cb34b73d64dde333c05c1fd24 from actual base 872337ab, adds explicit written 1–366-day guidance, a 90-day example, inclusive/exclusive comparison boundaries, missing-coverage/pagination cautions and the separate 31-day playcount-history maximum. This fixes the confirmed omission without changing the already-correct API or any of the twelve specification files. Four files change: maintained page, generated page hash, dated status and two regression cases.
Both regressions fail against the former frontmatter-only page and pass afterward. All 493 website tests, documentation regeneration/check, full TypeScript, focused ESLint, whitespace and required local production build pass. The tests compare prose with actual specification limits and verify maintained/generated/full-AI content retains it. The build uses only a synthetic public sign-in ID.
Next owners: UI performs independent exact-head review; Recoup OS owns qualifying merge; Docs regenerates retained publication only from the actual Marketing merge and verifies normal public AI text afterward. This remains open until final readback; no live measurement/customer/provider call, hosting mutation or stale-deployment claim. Proof: .local/audits/recoup-reconciliation-2026-10-10/catalog-range-ai-text-20261020/proof.json.
Current-main preservation refresh ready for narrow review
UI independently accepts the source at 12a16702b9749d9cb34b73d64dde333c05c1fd24 with 13 focused checks and both regressions failing against the prior page. After actual #200 merge 296b8501, #201 needed only a conflict resolution between its dated status note and the inventory note. Current exact head is 5204db25f26add8f65486363bdcf4d933e831904. Both entries and all current-main status bytes are preserved; the accepted range page, manifest and regression file remain byte-identical. The released index/archive/scripts/CI are retained. All 499 tests, inventory/docs checks, full TypeScript and required local build pass. Both refreshed CI workflows, Vercel, CodeRabbit and Cubic pass.
Next: independent narrow integration-delta acceptance and coordinator merge, then retained copy generated only from actual Marketing merge and normal AI-text readback. No repeated broad audit or manual host operation is needed. Receipts: .local/audits/recoup-reconciliation-2026-10-10/catalog-range-ai-text-20261020/refresh-delta.json and .local/audits/catalog-range-ai-independent-2026-10-20/acceptance.md. Complete #386 fan-publication receipts are preserved separately.
Activity