As of 2026-10-09. This checklist tracks the remaining work toward final delivery; a checked implementation item does not substitute for a verified release or live provider certification.
- Partial-output fallback suppression and explicit fallback policy
- Bounded fal cleanup and duplicate-submission prevention
- Standards-compliant, bounded SSE parsing shared by providers and TypeScript clients
- Cancellation and cleanup when consumers stop reading responses
- Provider credentials cannot follow redirects to an unconfigured destination
- Server streaming respects backpressure and contains asynchronous failures
- Orderly shutdown cancels active work and closes streams within a bounded grace period
- Resource retention and restart/recovery behavior are explicit and validated (local single-writer profile)
- Provider capability claims and configuration match supported adapter behavior (declarations, not live certification)
- Bounded account-visible model discovery/radar workflow is runnable and documented
- Scenario-evaluation and evidence-backed recommendation workflows are runnable and documented (functional checks, not official benchmarks)
- Fresh complete local gate and Node.js 22/24 compatibility evidence (current checkpoint)
- Complete public-content/history audit for the release candidate, including new artifacts (product-baseline scope audited; legacy identity disposition and final artifacts remain)
- Active GitHub CI with dependency audits, container verification and required checks
- Remaining dependency PRs resolved through compatibility evidence (integrated upgrades; #2/#6/#8 closed as superseded)
- Independently runnable provider-certification harness with sanitized evidence (protocol smoke only)
- Real-account adapter certification using authorized public-project credentials
- Reproducible release artifacts and a new versioned release with verification evidence
- Fixed-commit source artifact preparation, byte-for-byte reproduction and archive cold-start check (local checkpoint, not a published release)
- Final documentation and cold-start installation/run check from a clean checkout (verified at current toolchain checkpoint; future release deltas must rerun)
The latest checkpoint is source-release preparation: audited fixed-commit source artifacts, fresh complete local gates, Linux Node.js 22 artifact tests and installation/runtime verification from the extracted archive. The toolchain migration records the complete local and Linux Node.js 22 product gates with production-container smoke. The publication audit records disclosure scope/identity limits. Scenario evaluation records the focused Node.js 22 evaluation/config/CLI evidence. The broader Node.js 22 runtime baseline is bounded storage and restart recovery. Future runtime changes must rerun the relevant gates before these results support a release.
The reference runtime remains behind an authenticated gateway or on loopback. Tenant management, customer billing and a hosted SaaS gateway remain outside the owning project's contract. Public content must use public sources and synthetic fixtures; private implementation, accounts, credentials, routing policy, logs and business data are excluded.
The current GitHub credential lacks workflow-write permission. Live certification also requires dedicated, authorized public-project provider credentials; private-system credentials are not a substitute. These are open delivery gates, not completed or silently waived checks.