[Epic] Reconcile Recoup releases, docs, marketing, skills and plugins #318

Goal

Reconcile Recoup's supported implementation, public documentation, marketing, skills/plugins and operating instructions so users and agents can follow a documented workflow successfully, and future releases cannot silently leave those surfaces inconsistent.

Audit baseline and scope

• Window: July 10, 2026, 00:00 EDT through October 10, 2026, 20:17:09 EDT.
• Complete inventory of 1,185 merged PRs across 24 repository histories; the count includes parent reference updates and is not a count of distinct features.
• 47 source findings are mapped below into 38 actionable child tickets under six workstreams: 37 public coordination tickets and one restricted-repository follow-up. Related findings are grouped; some broad error-schema findings are split by affected consumer. Two child tickets cover prevention and final verification.
• Review covered current API contracts, both docs trees, marketing surfaces, skills/plugins, CLI and contributor/release instructions, with local checks and selected public GETs. No authenticated production customer/provider workflow was exercised as part of this audit. Complete PR metadata inventory does not mean every PR diff, changed line, or merged feature was reviewed or tested.
• This public epic contains sanitized platform findings and immutable public source evidence. Private client records and raw cross-repository audit archives are excluded.

User journeys this epic repairs

1. A developer discovers an endpoint or CLI command, follows its example, and receives the documented validation/result/error behavior.
2. An existing customer connects a supported agent through OAuth and discovers the tools appropriate to that connection without copying credentials into model instructions.
3. An artist workflow resolves the correct identity, uses valid creative inputs and follows real public skill dependencies.
4. A customer understands billing period, credit units, saved-card settings and usage line items, including recovery when a request is blocked.
5. A maintainer can identify the current source of truth, owning repository, supported package and remaining release acceptance.

Workstreams and native child hierarchy

• [Reconciliation] Documentation publishing and marketing #319 — Documentation publishing and marketing (4 child tickets)
• [Reconciliation] API, MCP and CLI contracts #320 — API, MCP and CLI contracts (9 child tickets)
• [Reconciliation] Chat, tasks and social workflows #321 — Chat, tasks and social workflows (4 child tickets)
• [Reconciliation] Billing, usage and pricing #322 — Billing, usage and pricing (7 child tickets)
• [Reconciliation] Skills and plugin distribution #323 — Skills and plugin distribution (7 child tickets)
• [Reconciliation] Release governance and regression prevention #324 — Release governance and regression prevention (7 child tickets)

Repair policy: implementation, documentation and product decisions

Fix the user outcome in its owning layer. Correct stale documentation promptly, but do not close a retained feature or runtime defect merely by documenting the broken behavior.

• Underlying implementation fixes: headless message validation ([Reconciliation][P2] Validate headless chat message parts before provisioning and fix the published schema #334), usage cursor gaps ([Reconciliation][P2] Prevent tied-timestamp charge loss and reconcile the usage response schema #345), payment-card/auto-top-up semantics ([Reconciliation][P2] Align card removal with the documented auto-top-up and fallback semantics #343), purchase billing-period handoff ([Reconciliation][P2] Preserve the selected Platform billing period through the purchase handoff #338 after price verification), public punctuation rendering ([Reconciliation][P3] Render punctuation correctly in the public skills browser #341), CLI input validation ([Reconciliation][P2] Match CLI validation and public command examples to the shipped API #355), and creative request validation plus the hosted lipsync worker/API audio integration ([Reconciliation][P1] Repair hosted lipsync, prevent silent creative-input loss and update skills #348).
• Finish retained capabilities: valuation persistence/history through API#795 and app#1911 ([Reconciliation][P2] Finish valuation persistence and history readback, then reconcile documentation #326); authenticated comments/fan-recency through app#2023 ([Reconciliation][P2] Restore the comments workflow and reconcile eleven stale API operations #327). Interim documentation corrections do not establish feature completion.
• Correct docs where the current implementation is intentional: Context coverage ([Reconciliation][P2] Publish the complete REST Context operation contract and MCP mapping #329), Sites publication/plan behavior ([Reconciliation][P2] Align Sites publishing and lifecycle documentation with the paid publication gate #330), stream range ([Reconciliation][P2] Document the supported 366-day catalog stream-history range #331), callback schema ([Reconciliation][P3] Resolve the undefined callbackSecret OpenAPI scheme #332), chat recovery contracts ([Reconciliation][P2] Correct chat resume completion and stop/retry response contracts #333), task plan/model behavior ([Reconciliation][P2] Document task read-time plan blocking and create-time model selection #335), social scrape behavior ([Reconciliation][P2] Correct social scrape defaults, follow-up bounds and authentication/error contracts #336), top-up/schema/credit units ([Reconciliation][P2] Make top-up schemas and examples satisfy the current request validator #342, [Reconciliation][P2] Complete the credits and subscription schema migration to three plans #344, [Reconciliation][P2] Reconcile billed feature coverage and social-scrape micro-dollar prices #346), and stale pin/music paths within [Reconciliation][P2] Restore the comments workflow and reconcile eleven stale API operations #327.
• Fix instructions or skill workflow logic: OAuth setup ([Reconciliation][P1] Replace legacy key-memory setup with consistent Recoup OAuth guidance #347), exact artist identity ([Reconciliation][P2] Use exact Spotify identity in roster onboarding and remove the obsolete ID workaround #349), billing recovery ([Reconciliation][P2] Reconcile credit-shortfall recovery across research, content and catalog skills #350), shared workspace guidance ([Reconciliation][P2] Correct the shared Skills checkout instructions for Business #353), sales/marketing references ([Reconciliation][P2] Refresh the marketing MCP note and sales catalog lookup recipe #354), and contributor guidance ([Reconciliation][P2] Reconcile required marketing instructions with the current product and Sky design #339, [Reconciliation][P2] Reconcile API, App and Docs contributor instructions with current architecture #356). A skill is executable agent guidance: wrong sequencing or identity resolution requires a workflow correction, not just edited prose.
• Repair distribution and release organization: one maintained docs source and publication path ([Reconciliation][P1] Finish the documentation cutover and restore the human MCP guide #337), generated editorial inventory ([Reconciliation][P2] Generate the published editorial inventory from the active blog source #340), real public music-video dependencies ([Reconciliation][P2] Replace missing public HyperFrames dependencies in the music-video skill #351), plugin metadata/maintenance policy ([Reconciliation][P2] Align legacy marketplace metadata and declare plugin maintenance ownership #352), public repository references ([Reconciliation][P2] Reconcile stale public Mono references through the owning release workflows #357), retired test-branch backlog ([Reconciliation][P2] Triage the 119 open API and App PRs targeting retired test branches #358), existing release acceptance ([Reconciliation][P2] Reconcile OAuth, roster and stream-history trackers with remaining acceptance #359), and the separately restricted workspace follow-up.
• Prevent recurrence and verify the result: focused contract checks ([Reconciliation][P2] Add release contract checks that catch drift across docs, skills and packages #360) and published/installed/original-user-workflow evidence ([Reconciliation][P2] Verify the reconciled release across public docs, installed clients and original user journeys #361).
• Explicit product decisions: Songstats retention and restoration are approved by Sidney on October 11 ([Reconciliation][P1] Retain research and restore Recoup-branded contracts #325); provider coverage, quotas and economics remain to verify before expanding usage. Verify the advertised billing offer before selecting its implementation ([Reconciliation][P2] Preserve the selected Platform billing period through the purchase handoff #338); decide unsupported specialized music/admin/song-write capabilities explicitly ([Reconciliation][P2] Restore the comments workflow and reconcile eleven stale API operations #327).

The 12 documented operations without matching method/path handlers consist of valuation history (#326) plus 11 operations in #327. Two of those 11 are stale pin paths whose capability already exists through PATCH; they are not two missing features. The 119 old test-target PRs are a triage inventory, not 119 missing features.

Evidence confidence and open questions

The finding-to-ticket map is a source-reconciliation backlog, not a list of 47 observed production failures. Priorities express triage judgment rather than measured outage severity.

• Corrections: hosted content/create still offers lipsync; removing the direct video mode selector did not remove every underlying capability. Two unmatched pin paths already have a PATCH replacement. The standalone package family has not been established as officially deprecated/unsupported. Calling it superseded was too categorical.
• Source versus deployment: method/path, validator, schema, instruction and Git-reference mismatches are tied to inspected commits. Except for specifically recorded public GET observations, this audit has not established which source behavior is deployed or what an authenticated customer experiences.
• Conditional runtime mechanisms: the usage cursor can skip response line items when timestamps tie; no production occurrence or lost ledger funds is established. Card-removal fallback depends on actual customer/card state; no real card or charge was tested. The hosted lipsync worker/API audio mismatch is a source-level integration finding; deployed preset execution remains untested.
• Provider/pricing unknowns: Songstats production/preview key configuration is confirmed and one local-key public search passed on October 11; secret-value parity, current agreement/activation, stats entitlement, quota, reliability and value remain unverified. The August 429 incident is historical. Actual Stripe recurrence, plan mapping, checkout availability and payment/webhook outcomes are unverified.
• Capability/distribution unknowns: a missing documented HTTP operation or dependency path is not proof that the capability is unavailable through every preset, MCP tool, connector, local workflow or installed package. Fresh host installs and auth-specific tools/list remain to verify.
• History/organization unknowns: a 366-day accepted range does not prove complete backfill. A main-branch Git reference gap does not prove stale production. The 119 old PRs still require diff-by-diff disposition; open feature trackers may correctly retain acceptance work, and all their comments were not reviewed.

Before closing any implementation finding, verify the intended behavior, reproduce the defect at the applicable source/deployed version, and attach the relevant original-user-workflow evidence. Correct invalid documentation promptly without retiring valuable capabilities merely to make a source comparison pass.

Execution order, priority and certainty

The sequence below covers all 37 public child tickets in 30 work packages. The restricted workspace follow-up stays in its owning private repository. This is the order for the identified audit backlog, not a claim that every merged feature has been exhaustively tested.

Confirmed means inspected source, recorded public output or a named local reproduction supports the specific mismatch. Verify means deployed behavior, provider/account state or actual user outcome remains untested. Decide means product/support semantics require an explicit disposition. Conditional source mechanisms are not observed customer incidents.

Priority favors setup, valid inputs before paid work, billing and retained customer outcomes. Investigations begin immediately alongside confirmed corrections. This execution sequence does not rewrite the child tickets' severity labels.

Start now

1. Establish the product baseline — Verify. Capture deployed API/App/worker and installed package versions, then classify the complete API/MCP contract inventory. #361, #360.

2. Establish one documentation authoring path — Confirmed + verify. Continue marketing#101's existing direction; reconcile 15 missing/eight differing files against product and preserve intentional pricing distinctions. #337.

3. Repair authentication and MCP setup instructions — Confirmed + verify. Repair supported installation/OAuth/REST/organization guidance, remove retired tool examples, and replace fixed catalog counts. #347, #328.

4. Repair creative contracts and preserve hosted lipsync — Confirmed + verify. Correct creative inputs and pre-billing validation; preserve the hosted lipsync preset and verify its actual audio/dispatch/composition path. #348.

5. Correct billing schemas, amounts and recovery examples — Confirmed. Correct top-up inputs, micro-dollar units, plan responses, billed-feature coverage and billingUrl recovery. #342, #344, #346, #350.

6. Fix headless message validation — Confirmed/local reproduction. Validate parts-based headless messages before provisioning and repair examples/error schemas. #334.

7. Retain research and restore Recoup-branded documentation — Confirmed decision + verify. Restore all 15 removed reference operations against current validators/adapters, preserve the existing integration/key, correct confirmed runtime defects, then verify quotas, coverage and economics before increasing usage. #325.

Product repairs

8. Repair usage pagination — Confirmed mechanism + verify. Reproduce timestamp ties and use a stable time/id cursor; verify complete response pagination against independent totals. #345.

9. Repair payment-card removal semantics — Confirmed omission + decide/verify. Set intended multi-card/customer and immediate auto-top-up behavior, then repair implementation and readback. #343.

10. Repair the pricing-to-purchase handoff — Confirmed handoff loss + verify. Verify the actual Stripe offer/recurrence and preserve selected monthly/annual intent through the approved purchase flow. #338.

11. Finish valuation history and comments/fan recency — Confirmed integration gap + verify. Finish retained valuation persistence/history and stored comments/fan-recency through existing work; documentation deletion is not delivery. #326, #327.

12. Resolve the remaining stale operation paths individually — Confirmed paths + decide. Use PATCH for pin/unpin; decide supported disposition for specialized music, song-write and admin reporting paths. #327.

Supported contracts

13. Publish the complete Context contract — Confirmed coverage + verify. Document supported Context actions, I/O, REST-to-MCP mapping, authorization, readiness, cost and errors. #329.

14. Correct Sites publication and lifecycle documentation — Confirmed contract + verify. Correct paid publication, recovery, lifecycle/revision tokens, deletion, uploads, consent and public snapshots. #330.

15. Correct catalog stream-history coverage — Confirmed range + verify. Publish the supported catalog-history range while preserving the separate playcount limit and honest completeness language. #331.

16. Correct chat resume/stop contracts — Confirmed contract + verify. Correct resume SSE, stop behavior, cancellation failures, timeouts and active-run/error schemas. #333.

17. Correct task contracts — Confirmed contract + verify. Correct task plan-limit reads, optional model, defaults, timezone and run linkage. #335.

18. Correct social scrape and fan-discovery contracts — Confirmed defaults + verify. Correct platform-specific scrape depths, fan workflow/run-bound claims, budgets, ownership and errors. #336.

19. Align CLI guidance and input validation — Confirmed parser + verify. Align command examples and local validation, then verify published package/version and the intended host. #355.

20. Correct artist identity and roster guidance — Confirmed guidance + verify. Resolve exact Spotify identity before canonical create/attach; document legitimate manual onboarding and repeated-attach behavior. #349.

21. Repair public music-video dependencies — Confirmed dependency gap + decide. Ship real public composition/verification dependencies or a supported packaged alternative. #351.

22. Align plugin distribution and ownership — Confirmed metadata + decide/verify. Align install IDs, registries, child versions and source ownership; declare supported versus legacy/migration status explicitly. #352.

23. Classify undocumented routes and resolve callback authentication — Confirmed schema + decide. Disposition all 57 no-spec operations, document retained public ones and fix callbackSecret or move the callback contract to its proper audience. #332, #360.

Publishing and release

24. Add checks alongside each repair — Prevention; tooling choice. Add focused examples/schema/parser/package/provenance regression checks with each repair, rather than waiting until the end. #360.

25. Complete the canonical publishing cutover — Confirmed drift + verify. Refresh marketing#101/Update Seeker eval dashboard visuals #124, preserve open docs work, rebuild every output, diagnose /mcp, then verify the established redirect/cutover path before freeze/archive. #337.

26. Verify original user journeys and published output — Verify. Verify final published guides and installed/deployed original user journeys with named versions and explicit unresolved gates. #361.

Maintenance alongside core work

27. Reconcile contributor and operational instructions — Confirmed. Update product/design/pricing/auth/branch/authoring context, shared Skills checkout guidance and sales/historical MCP recipes. #339, #356, #353, #354.

28. Repair editorial inventory and skills-browser punctuation — Confirmed. Generate editorial inventory from active source and repair literal Unicode escape text in the public skills browser. #340, #341.

29. Reconcile public Mono references — Confirmed refs + verify. Verify intended released baselines, then update selected public Mono references through owning repository/Mono PRs. #357.

30. Triage relevant old work and reconcile release trackers — Confirmed metadata + verify/decide. Triage the 119 retired-test PRs against current main and reconcile full tracker discussions before porting, retiring or closing work. #358, #359.

Independent repairs and maintenance can proceed in parallel. Apply the authoring/instruction policy and prevention checks immediately; publish urgent confirmed corrections incrementally. Retained capabilities remain open until delivered or explicitly deferred with an owner.

The canonical destination follows existing marketing#101; preserve and refresh marketing#124 as part of that work. Do not blindly mirror either docs copy, overwrite intentional commercial/technical distinctions, archive outstanding work or infer that a docs host migration fixes API behavior.

The final verification child depends on applicable releases. Existing OAuth, plugin purchase, payment/fulfillment and client-discovery gates remain with their current trackers. No source check or merge alone establishes a deployed customer outcome.

Execution of packages 1–7 — October 11, 2026

All nine original PRs and the separately approved fixture-only API #1030 are merged. Mono #367 records the five released repository references at commit 719bf3ba13e2799f5860f82f910f90ddf9d213dd; Skills reference updates remain owned by the existing coordinator.

This release includes runtime repairs, documentation/schema corrections and updated agent instructions. Acceptance remains scoped: merged code, deployed services, published packages, installed clients and original customer workflows are recorded separately.

Released PRs and versions

• API #1028 plus fixture-only API #1030: reconciliation release commit 2a882dd460ef6757af6d7b1b93bbc1fd8d0c6e86.
• Tasks #157: production deploy run 38165733100, worker 20261011.1.
• Marketing #149: production READY at 4897009f2007af8ecac0d70535ed53950d1010d3.
• Docs #372: merged d688d2dd06caebea7bbc91be761311d903a24de0, pinned to that actual Marketing merge.
• Skills #183: published package 2026.1011.7 from 93eb0c448e17038d50c95ebd923247c500bcbe80. Downloaded customer ZIP checksum matches the release manifest; 40 customer skills, no internal skills, and three sampled guides match reviewed source.
• Platform #5: 0.2.1 at bb9f6bc4a05deb251df86c0781ef77422c1523f3; Content #2: 0.3.1 at 9d3cf8120a457a3ed84643e174e6cd8f49d96dac; Research #5: 0.2.1 at e9a306715cdf7e36e21040e4a47ee0f5efd8f76f.
• Marketplace #14: both host registries and matching Gitlinks pin those actual plugin merges; registry merge e346cf456fb1a29baae1296038c39a8a8519d691. Catalog version and its previous Stop-hook removal are preserved.
• Mono #367: merged release references at 719bf3ba13e2799f5860f82f910f90ddf9d213dd.

Validation: 102 focused API tests, seven shared copyable request fixtures, 365 worker tests, 427 Marketing tests, seven docs checks, all five Skills publishing gates and fourteen mocked workflow regressions passed. Marketing's approved remote build validation passed and its production deployment is READY. Worker type checking retains eight existing errors versus nine at base; no new signatures were introduced.

Publication and remaining gates

Final October 11 production readback: API is READY at 925a57a704c7a9e32ee817e040b47a99ca144dd1 and Marketing at 8b36ab7677e3bd34c33e39f499518a301a2230c9. GitHub comparisons show each is one commit ahead of the reconciliation release, with no reconciled API-route or documentation-source changes: API comparison, Marketing comparison. Immutable release/provenance pins remain the reviewed reconciliation commits.

Canonical public evidence: Research availability, research reference, human MCP guide, credits, LLM index and full LLM content. All 15 restored research Markdown references returned 200 and contained no data-provider names. Later Marketing production updates changed only podcast content, leaving this documentation source unchanged.

Hosting work remains deferred by Sidney. October 12 readback now confirms the retained host publishes Research availability, its Markdown, research search Markdown and both LLM catalogs at HTTP 200, without research-provider branding. The human GET https://docs.recoupable.dev/mcp still returns 405; /mcp.md and the canonical Marketing human guide return 200. The October 11 restored-page 404s are historical rather than the current state of these checked pages. Final route/host compatibility and complete publication verification remain open.

The task's installed workspace Skills cache remains 2026.1011.1 and still contains stale account-ID guidance. Do not manually patch the cache: fresh installation/upgrade and readback of 2026.1011.7 remain in #361. GitHub ZIP publication is not OpenAI directory approval or installed-client verification.

The prior production-search receipt mistakenly read data.artists rather than the top-level results array. Its zero counts were a receipt parsing error. The corrected bounded search readback is HTTP 200 with five results and five usable generic IDs; no claim of full provider coverage follows.

The superseded retirement tracker and API removal PR #875 must not remove the retained integration, credential or table. Provider names, credentials and private commercial terms remain out of public product guidance. DNS/cutover/archive, broader packages 8–30 and commercial/provider expansion remain separate.

Definition of done

• Every finding has a linked child outcome: fixed and verified, intentionally retired, or explicitly deferred with an owner and rationale.
• One documentation authoring policy is declared; retained public HTML, Markdown and LLM discovery agree with the supported contract.
• Copyable API/CLI/skill examples pass appropriate provider-free contract checks; runtime fixes have focused regression coverage.
• Supported plugin names, versions, install/authentication paths and dependency links agree with shipped artifacts.
• Existing feature issues show implemented versus remaining acceptance; no issue is closed solely because code merged.
• Final public/installed/user-flow evidence is linked with version and scope; unavailable or unauthorized tests remain explicit open gates.
• Prevention checks have an owning repository and cover the regressions that escaped existing snapshot/vendor validation.

Finding-to-ticket map

Status at creation: merged-PR inventory and targeted source reconciliation complete; authenticated feature verification incomplete; repair work planned. Native sub-issues and the mapping above are the coordination record.

October 12 follow-up: #346 has a confirmed residual source-description/comment unit defect despite corrected examples. Its affected acceptance criteria are unchecked again. The confirmed remaining contract-documentation work is #329, #330, #331, #332, #333, #335 and #336 (with Sites paid-publication text already corrected), CLI/instruction work #355/#356, and routing/publication compatibility #337. Product-dependent obsolete-operation decisions remain #326/#327.

Source corrections released — October 12, 2026

The following remaining-docs batch preserves the priority order discussed with Sidney. These source corrections are merged; the release and remaining acceptance are qualified below.

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.

No feature-acceptance child is closed merely because these PRs exist. Remaining product and verification work includes valuation persistence/readback, comments/fan-recency, specialized music/song/admin contracts, provider-neutral Context module inputs, complete hosted Context, real lipsync artifact inspection, supported-host OAuth/installed clients and remaining research/billing reliability. Mintlify repair/cutover stays deferred.

Remaining execution batch: fixes, certainty and release order

The billing defect is an underlying implementation fix, not only a docs correction. No historical customer billing discrepancy is asserted from the local reproduction.

Four prepared PRs: API #1033, Marketing #153, Docs #374, and Skills #191. All required checks pass; API and Marketing final-head Vercel previews pass. Docs’ Mintlify preview check is skipped, so no Mintlify publication is inferred. These PRs remain unmerged pending the explicit API merge approval required by AGENTS.md:15.

The final Marketing preview at a45046d8 returns 200 for all nine checked HTML/Markdown/spec URLs; the corrected cursor and credit examples appear in each format, and all three specs exactly match source. Docs at 8adb301e verifies all 231 managed files/navigation against that Marketing review pin. After approval, merge API first, refresh Marketing’s API source pin, then merge Marketing and refresh/merge Docs from the actual Marketing merge. Skills release is independent; its Mono reference remains owned by the existing coordinator.

Final API CI at e37e1579: 6,407 tests pass, 13 environment-dependent tests skip; lint, format, OAuth compatibility and Vercel pass. Marketing: all 441 local tests and docs/contract checks pass; final preview build/readback passes. Skills: all five required gates, 24 package tests and a local build (40 customer / 118 full skills) pass. Verification used local fixtures and read-only live checks, with no paid scrape/generation, outbound messages, real charges or production data mutation.

CLI npm publication still waits for Sweets: registry version is 0.1.15 and the NPM_TOKEN update timestamp remains June 25. Mintlify routing/connection/cutover repair remains explicitly deferred. Broader OAuth lifecycle/organization/client, hosted Context ingestion, real lipsync media, research coverage and purchase-fulfillment gates remain open. Source preparation and a passing preview do not close production acceptance.

Approved release completed — October 14, 2026

All four approved PRs are merged: API #1033, Marketing #153, Docs #374 and Skills #191. Mono #387 records the three platform references at 52d71b26. The actual immutable source chain is API 4dd30758 → Marketing 5cb01c9a → Docs b778f7bd; Skills merge is 4b1ac620 and its Mono reference remains with the coordinator.

Verified release: API and Marketing main checks pass, and their canonical production aliases are READY at the actual merge deployments. Live read-only usage returns a composite time/ID cursor, six-digit microseconds and two distinct paged events with identical period bounds; limit=101 returns 400. Timestamp ties, period-total reconciliation, cost ties and failed-start debit behavior are verified with local regression fixtures rather than invented production billing observations.

Canonical usage and both scrape references return 200 in HTML, Markdown and split OpenAPI, contain corrected examples, and all three specs exactly match released source. All 231 retained files/navigation verify against the actual Marketing merge. Mintlify's automatic main deployment succeeds; after it finished, all six selected normal retained Markdown/spec URLs return 200 with corrected examples, and all three specs exactly match source. The earlier stale readback preceded that completed deployment. No hosting repair or cache purge was performed.

Plugin release 2026.1014.14 publishes from the actual Skills merge. The downloaded customer ZIP matches the manifest SHA-256 and contains 40 customer skills with no internal entries. The separate installed-Claude/source/discovery checks remain recorded in the October 13 receipt; package publication does not establish every client or OAuth lifecycle.

Remaining: npm still serves CLI 0.1.15 and NPM_TOKEN's update timestamp remains June 25, so the publishing repair waits for Sweets. Mintlify routing/connection/cutover repair remains explicitly deferred; human MCP and full-LLM cache compatibility were not re-audited in this batch. Broader OAuth organization/lifecycle/other-host, hosted Context ingestion, real lipsync artifact, research-coverage and purchase-fulfillment gates remain open. No paid scrape/generation, outbound message, historical billing discrepancy, refund or production data mutation is asserted.

Ticket outcome: Completed children in this batch: #332, #336, #345 and #346. The epic remains open for the remaining workstreams and acceptance gates recorded below.

Reconciliation refresh — October 18, 2026

The actual reviewed source chain is API 4f721f8e → Marketing 7febcce4 → Docs 616937ef; API ancestry independently confirms inclusion of both other API merges. Docs' provenance was independently read and names the Marketing merge and 235 files.

Unresolved error-message safety: #1038 deliberately preserves token-verification exception text, and #1039 preserves raw provider exception text. Matching existing response schemas does not prove those messages are safe. Keep sanitization plus generic public messages/server-side diagnostics as an unresolved follow-up under the existing contract/prevention work; the new fixtures do not close it.

Remaining customer outcomes: card-removal/automatic-purchase semantics #343 and monthly/annual purchase selection #338 remain open; these merges do not implement either. Connected Context acceptance is now recorded under existing #361, alongside #329 and original Context app #2116/#2140. Read-only exact-snapshot comparison comes before controlled save/access/workspace tests. No new epic or competing queue is created. Existing #346 stays closed for its completed October 14 outcome; #1039 is additional structural hardening, not proof of a historical charge or refund.

Evidence boundary: GitHub merge states and final-head checks were refreshed on October 18. Test counts and preview observations above are attributed to the implementation PRs; this pass did not rerun their suites or call customer/provider workflows. No production deployment, database migration, credential cleanup/rotation, paid action, client import, or automatic merge was performed. October 14's live release receipt remains dated evidence for its own versions, not proof of this newer source batch.

Existing-assessment read checkpoint — October 18 follow-up

The earlier source-only refresh is now supplemented by a bounded read-only pass from Records and MCP. The existing saved assessment reopened through the production web assessment viewer and connected Recoup tools. Its 1,034-character summary, citations, visible subject/source references, partial coverage and six missing topics match. MCP independently reopened the exact saved snapshot and matched the previously recorded input manifest. Protected IDs, contents and hashes remain in the owning private receipt.

Still unverified: complete structured-manifest parity across web and MCP. The web viewer does not render document/result IDs or structured document versions. Document version 1 is verified in MCP only; the accepted assertion is not verification of metadata or rights. This result does not complete controlled saves, retries, other-company denial, revocation, withdrawal, supersession or file-conflict checks.

The runtime handoff identifies API production e4d9b6902879936e5a5f159dab85acd4f82cfb48 and web production d13bdcb7b112ff0ed8d9d243ae7c6fd56f9a80d4, both READY, with deployment receipts. This is reported owner evidence inspected by Docs, not a fresh deployment initiated here. Recoup database applied migrations/function grants and the MCP response's server/client build remain unverified.

Next: under existing app #2116, expose read-only provenance in the existing assessment viewer and repeat the exact-snapshot comparison; #2140 retains evidence-intake policy. Existing #361 records the version prerequisites and pass/unknown/not-exercised states. The guest funnel's Save claims a request; the separate assessment viewer already calls save_brief/read_brief. Do not mistake one for the other or infer no web snapshot operation exists.

No deployment, production write, credential rotation, paid action, import or merge was performed by this documentation follow-up. The epic remains open.