Customer-facing changes and compatibility notes. The README owns current pricing, source coverage and recovery guidance. A saved task can retain an older build.
October 8, 2026 — maintenance update in the 0.4 family
Updated the application build and starting guide. Watched-contract review, dated source coverage, optional pipeline summaries, prices and limits are retained. This is not a new real-time opportunity feed or a promise that bids are open.
0.4.0 — October 4, 2026
See what your pipeline is made of. The optional Review-mode brief separates repeated records from consistently identified contributions across up to 100 supplied rows. Conflicting revisions, missing relationships and unknown amounts stay visible.
Forecasts, obligation assertions and ceiling assertions remain separate by currency and period. The official source model does not supply financial amounts; your totals are not verified revenue or award predictions. Pipeline rows add no billing units, source requests or private-system connections. Monitor does not compare pipeline history.
0.3.0 — October 2, 2026
Clearer recovery after an interruption. Pending or unknown publication, history and charge outcomes are no longer described as unattempted or zero. Re-entering the same interrupted run does not submit results or charges again. Inspect saved results before starting a separate review.
The source reader reuses working storage, with the same evidence boundaries. Local component measurements do not establish faster or cheaper hosted runs. Follow original notices for current deadlines and amendments.
0.2.0 — September 25, 2026
Review dated SAM notice snapshots. Supported source editions add notice relationships and visible coverage information to the contract review. Missing, damaged or unsupported required evidence does not become a completed billable review.
Repeated reviews can use an explicitly selected history store. This does not create a schedule. Authenticated SAM API description coverage remains a separate capability; the supported snapshot route does not depend on it.