Delta Signal ATLAS-7 Changelog

Universal evidence contract

Add one mandatory provenance object across readiness, company report, daily changes, evidence drilldowns, alpha signals, fundamentals, peer ranking, covenant stress, and SPECTRA. Missing fields should return null, not disappear.

• Fields: captured_at, observed_at, published_at, data_as_of, computed_at_utc, source_date, accession_number, evidence_ref, evidence_hash, schema_version, contract_version.
• Add semantic daily-change deltas with field_path, prior_value, new_value, delta_type, threshold_crossed, materiality_score, and evidence identifiers.
• Document whether evidence refs are stable, what evidence hashes cover, how pagination affects hashes, and whether refs can be replayed after refresh.

Scale and freshness ergonomics

Add preflight and batch surfaces so clients do not need repeated paid single-name calls just to discover coverage, freshness, or availability.

• Add GET /v1/companies, GET /v1/companies?changed_since=..., and GET /v1/ticker-freshness/{ticker}.
• Extend company-report bundle support to tickers: [] with per-ticker result, partial flag, provenance, and error state.
• Add snapshot metadata for company reports: snapshot_id, start/end timestamps, section count, max section skew, and whether sections share the same data-as-of boundary.

Monitoring and contract maturity

Move from pull-only reports toward durable monitoring and explicit field stability.

• Add webhook/subscription routes for material changes with event IDs, delivery signatures, replay cursors, field deltas, provenance, and evidence refs.
• Add GET /v1/contract/changelog and GET /v1/contract/fields for stable field paths, deprecation windows, migration notes, and versioned daily-change fields.
• Document route classes: free discovery, cheap freshness, paid compact, paid evidence, and internal/backend-relayed access.
• Constrain renderer posture values to non-advice labels such as constructive_evidence_screen, watchlist_candidate, risk_elevated, provenance_limited, data_stale, and insufficient_evidence.

Calculation-plane receipts and semantic MCP public contract synchronized

The public plugin now reflects the final issuer-wide replay, the separate customer-route regression audit, and the governed semantic MCP catalog instead of preserving older route and coverage counts as current.

• CompanyFacts/PIT replay: 378 of 378 issuers, 817,992 materialized rows, and 0 errors.
• Customer audit: 215 issuers, 1,935 operations, 1,923 successful, 0 failed, 0 skipped, and 12 not applicable.
• Live discovery: OpenAPI 1.5.2 with 68 paths; MCP with 81 tools including 26 governed semantic tools; pricing with 30 routes; field contract with 47 fields.
• The 378-issuer replay and 215-issuer route audit remain separate evidence scopes, and semantic tools return governed evidence envelopes rather than raw SQL.

Circle Agent Marketplace readiness made first-class

The landing page, README, and LLM changelog now frame Delta Signal ATLAS-7 MCP as an x402-compatible seller service for Circle Agent Marketplace review. The public copy surfaces standard Base x402 compatibility, Circle Gateway GatewayWalletBatched, no-public-API-key integration, signed grant-session separation, per-call receipt reconciliation, and the non-broker / non-advice boundary.

Circle Gateway x402 compatibility guidance published

Public docs now state that standard Base x402 remains the compatibility path, Circle Gateway is the optimized path for Circle-aware clients using GatewayWalletBatched, and grant-covered calls remain backend virtual credit rather than on-chain settlement.

Design-partner grant expiry fields and Natural Language route coverage deployed

Production now exposes the actual grant-window expiry fields separately from the short signing-challenge TTL, and grant-covered Natural Language routes use the same signed-session grant path as structured Delta Signal routes when the active grant contract includes them.

• GET /v1/grant/challenge, POST /v1/grant/session, and GET /v1/grants/status can expose grant_expires_at and grant_expires_in_seconds for the grant window.
• grant_runway_authoritative_fields now includes grant_expires_at alongside USD runway fields when the caller context has an active budget grant.
• expires_at and expires_in_seconds on challenge/session responses remain the short signing/session TTL fields, not the grant-window expiry.
• Grant contracts can now cover GET /v1/morning-brief/natural, GET /v1/top-stressed/natural, and GET /v1/covenant-stress/natural through the signed wallet grant-session flow.
• Exact public route matching now resolves /v1/covenant-stress/natural before templated ticker routes such as /v1/covenant-stress/{ticker}.
• Plain unsigned wallet headers still do not unlock grants; signed grant-session tokens remain the authorization artifact, and x402 fallback remains the correct path when a grant is unavailable, expired, exhausted, or not route-eligible.

Design-partner grant runway and expiry contract clarified

The public contract now clarifies that design-partner grant runway should be sized from grant_budget_usd and grant_remaining_usd, that grant_limit is only a compatibility view, that route-priced grant debit is server-side, and that issued design-partner grants expire 30 days after issuance unless separately renewed.

• Budget-grant sizing uses grant_budget_usd and grant_remaining_usd as authoritative USD runway fields.
• grant_limit and grant_credit_equivalent_* remain compatibility fields and must not be treated as raw USD or request count.
• Grant-covered calls debit server-side by route-declared price; clients should read server runway instead of reconstructing decrement math from local call logs.
• Fresh and cached covered reads should not be assumed to debit differently unless the live contract changes.
• The design-partner grant is separate from client-side x402 monthly caps; x402 spend starts only when the grant is unavailable, expired, or exhausted.
• Design-partner grants expire 30 days after issuance unless a separate renewal or replenishment is explicitly issued.

Audit-grade Natural Language Morning Brief renderer deployed

Production now serves audit-grade Natural Language Morning Brief output from Azure revision ca-web-intel-mcp--0000527, with score interpretation, concrete risk-distribution snapshot, stale source-period caveats, safer route recommendations, and cached/precomputed MCP reuse.

• Deployed revision ca-web-intel-mcp--0000527 from commit 981f25ae415fadd702208ec85be0ecc86e9ca95b using image acrgniwebintel001.azurecr.io/ca-web-intel-mcp:skill-20260616071440 and digest sha256:e2587e0f130987759c897531c839091cfd71a62938b663284afc263a802f2a82.
• Natural brief output now includes Score Interpretation for Stress 50%, Risk Tier, Alpha Score, Board Rank, and Resilience Percentile so readers understand what each numeric field means.
• Market-Wide Risk Board now renders bucket counts and percentages when risk-distribution data is present.
• Top-stressed rows now flag stale source periods relative to the daily-change reference date instead of presenting older issuer metrics as same-day evidence.
• Evidence limits now explicitly state compact evidence mode, source-date boundary, screen-not-recommendation status, and missing-evidence behavior.
• Drilldowns now prefer Company Report, raw covenant stress, daily-change evidence, and issuer fundamentals; natural covenant stress is only referenced when current route metadata marks it live.
• Live MCP probe verified cache_hit=true, source_date=2026-06-16, model=deterministic-atlas7-nl-renderer, tokens_used=1652, latency_ms=174, and cost_usd=0.95.

Claude Code MCP project guide added

The repository now includes a full CLAUDE.md guide for Claude Code work on the Delta Signal ATLAS-7 / SPECTRA / x402 / TripCode research-agent stack.

• Added project-level Claude Code instructions for MCP install, first-run readiness, composite-first tool use, granular route discipline, x402 payment boundaries, Google Cloud / Gemini boundaries, and final answer shape.
• Preserved strict evidence labeling: filing-backed, Delta Signal MCP evidence, article-derived, inference, missing/unresolved, user-provided context, and unfetched drilldown.
• Captured refusal rules for personalized investment advice, unsupported financial claims, TripCode identity misuse, payment/wallet abuse, secret exfiltration, unsafe repo operations, fetched-evidence misrepresentation, and public-subscriber overclaiming.
• Included the HUT TripCode known local validation case while preserving the public-readiness caveat for missing newer MCP deployment and River/index blobs.

Coinbase x402 and Codex marketplace reviewer positioning

The public docs and marketplace metadata now frame Delta Signal ATLAS-7 as a Codex-ready, x402-payable issuer-intelligence evidence service for reviewers: install, discover, inspect route metadata, trigger 402, retry with proof, and inspect provenance.

• Added reviewer-facing checklist language for MCP discovery, OpenAPI route contracts, Arazzo workflows, x402 challenge/retry behavior, Bazaar metadata, route pricing, and non-advice boundaries.
• Focused marketplace review on the public ATLAS-7 surface: readiness, Morning Brief, Company Report, Pressure Board, Alpha Sweep, Quick Ticker Check, daily changes, issuer fundamentals, covenant stress, peer ranking, alpha signals, and SPECTRA field maps.
• Adjusted plugin and MCP registry metadata so TripCode/River subscriber research is not advertised as public marketplace-ready unless live MCP discovery exposes those tools.
• Kept the Agentic Market / Coinbase first-party verification boundary explicit: no branded verification claim until Coinbase or the relevant UI confirms it.

LLM evidence-routing guardrails and TripCode discovery caveat

The LLM handoff files and plugin skill now explicitly separate ATLAS-7 as the SEC/XBRL evidence layer, SPECTRA as the ATLAS-history field-map layer, and TripCode/River research as discovery-gated unless the live MCP tools and required River/index blobs are present.

• Updated llms.txt and llms-full.txt with strict evidence routing, preferred broad/issuer/daily/TripCode workflow order, metadata preservation rules, and hard non-advice prohibitions.
• Updated the bundled DeltaSignal skill instructions so agents check live MCP tools/list before claiming TripCode tools are public-production callable.
• Documented the HUT TripCode boundary: local/source proof may exist, but public execution still depends on deployed MCP discovery plus the required TF-RIVER-HUT and by_issuer/HUT resolver blobs.
• Preserved public-safe language and avoided private design-partner details, wallet addresses, mailbox details, secrets, or personalized financial advice.

Live readiness and MCP evidence hardening deployed

Production now serves the hardened DeltaSignal readiness and MCP evidence surface from Azure revision ca-web-intel-mcp--0000484, with 56 OpenAPI paths, live pricing discovery, live field-contract discovery, structured invalid-path-scope errors, and a 97.5% cmd/search-gateway source coverage checkpoint.

• Deployed Azure Container App revision ca-web-intel-mcp--0000484 from clean git-archive source commit 4cb93a38b9a438055caf279e51474b86db737c62 using image acrgniwebintel001.azurecr.io/ca-web-intel-mcp:skill-20260608045057 and digest sha256:0e2a137494de91fb4471226ee6e58269dcb1564d3ac3b6d156ff94b7e39203b7.
• Post-rollout live probes verified /health 200, /openapi.json with 56 paths, /v1/pricing 200, /v1/contract/fields 200, /v1/events/latest present, and HUT company-report plus SPECTRA field-map routes protected by expected public x402 402 challenges.
• No-ticker universe misuse is now explicit: /v1/readiness/UNIVERSE and /v1/daily-changes/latest/UNIVERSE return HTTP 400 invalid_path_scope with billing_behavior=not_charged, cost_usd=0, path_ticker_free=true, and deltasignal-route-scope-v1 metadata.
• The HUT-driven evidence-readiness slice documents company-report envelope fields for agent consumers: issuer_evidence_envelope, evidence_sections, spectra_metadata, publication_audit_block, route_uri, source_date, computed_at, caveats, quality_flags, and non-advice boundaries.
• Local verification before deploy passed go test ./cmd/search-gateway/... with coverage profile at 97.5%, plus gofmt check, secret scan, whitespace check, deploy audit, and post-rollout smoke probes.
• Public boundary: this entry contains only public-safe route, revision, coverage, and contract metadata. It excludes private design-partner names, mailboxes, wallet addresses, grant amounts, and support artifacts.

SPECTRA generation model documented

The public docs now explain SPECTRA as the field-map contract layer derived from ATLAS-history-shaped rows: ticker/source-date resolution, numeric/date/boolean normalization, pressure and range labels, provenance, caveats, and structured soft-miss behavior.

• SPECTRA does not create a second evidence source; it derives an inspectable field-map contract from generated ATLAS-7 history and point-in-time rows for a ticker.
• The generation path resolves source date and issuer identity, normalizes scalar values and date bounds, derives pressure/range labels, and packages the field map with provenance and caveats.
• When rows or contracts are unavailable, SPECTRA should preserve structured not_found or historical_field_map_contract_missing behavior instead of fabricating a field map.
• Agents should use /v1/spectra-field-map/{ticker}, /v1/atlas-history/{ticker}, and /v1/point-in-time-history/{ticker} when they need generated history or field-map explanation.

ATLAS-7 generation model documented

The public docs now explain ATLAS-7 as the generated issuer evidence layer: EDGAR CompanyFacts mirror or reconstruction, process-changes deltas, crypto-exposed issuer matching, ticker/CIK normalization, dated evidence rows, calculation history, and MCP-safe evidence outputs.

• ATLAS-7 starts from the daily EDGAR background task, not request-time scraping: CompanyFacts ZIPs, daily feed recovery, full-index context, process-changes artifacts, and manifests define the evidence boundary.
• The pipeline matches the crypto-exposed public-company universe, normalizes issuer identity by ticker and CIK, and emits dated issuer rows used by readiness, daily changes, company reports, pressure boards, alpha screens, peer ranking, and history routes.
• Generated ATLAS-7 evidence carries source dates, caveats, quality flags, manifests, and non-advice boundaries so MCP clients can cite returned evidence without inventing missing facts.
• The product page now exposes this generation chain directly in the architecture surface for users and agent readers.

EDGAR trading-week audit and 2026-06-02 reconciliation

The June 1-5 trading-week audit is now complete: all five business dates have CompanyFacts ZIP coverage, delta summaries, digital-assets delta artifacts, and recorded status, with 2026-06-02 classified as recovered_reconciled after daily-feed reconstruction.

• Final audit totals for 2026-06-01 through 2026-06-05: date_count=5, zip_count=5, delta_summary_count=5, digital_assets_delta_count=5, change_blob_count=565, complete=4, recovered_reconciled=1.
• Daily rows: 2026-06-01 complete with 174 change blobs and 111 digital-assets companies; 2026-06-02 recovered_reconciled with 2 change blobs and 1 digital-assets company; 2026-06-03 complete with 149 and 87; 2026-06-04 complete with 113 and 77; 2026-06-05 complete with 127 and 80.
• Audit artifacts were written to artifacts/deltasignal-atlas7-backfill-cleanup/20260606T204221Z/backfill-window-audit.json and backfill-window-audit.tsv for local operator evidence.
• Focused worker tests now cover the CompanyFacts readiness wait helpers, duration/null helpers, explicit XBRL extraction edge case, extra crypto CIK merge branches, and the daily-feed-only reconciliation summary path; full package coverage remains a separate open goal, not a completed claim.

CompanyFacts daily-feed reconstruction restore path

The recovery log now documents the fallback used when SEC companyfacts.zip does not advance for a business date: if full-index, daily-feed, and prior baseline artifacts exist, the worker reconstructs the missing CompanyFacts ZIP from the daily feed, validates it, and records reconciliation policy before promotion.

• For missing 2026-06-02, the canonical recovery path used daily-feed reconstruction because 2026-06-01 was mirrored, 2026-06-02 full-index and daily-feed data existed, and the SEC CompanyFacts ZIP was not yet advanced for that date.
• The reconstructed output sha256 is 3e5042d8d8912a96b16022bb576d640c871e04456b8500421625ee692ae4b337 with 2144564771 bytes, 369 affected CIKs, 97 patched JSON company facts, and 130 parsed filings.
• The reconciliation summary records policy=daily_feed_reconstruction_canonical and preserves warnings that no future-ZIP continuity summary was available for this restore.
• This turns a missing CompanyFacts business date into a documented recovery state instead of a silent gap in downstream MCP evidence.

EDGAR daily background task foundation log

The changelog now records the EDGAR daily background task as the basis of the Delta Signal MCP: every Morning Brief, daily-change drilldown, issuer report, pressure board, and notification summary depends on the CompanyFacts mirror, process-changes artifacts, manifests, and evidence metadata generated by that task.

• The daily job starts after the US trading day, normally around 11:00 PM Pacific time, and waits for SEC companyfacts.zip to advance before running the full process-changes pipeline.
• The worker mirrors canonical CompanyFacts ZIPs into Azure under companyfacts/{date}/companyfacts.zip, then writes delta summaries, per-CIK change blobs, intelligence artifacts, and run manifests for the MCP layer.
• MCP surfaces consume those artifacts instead of scraping at request time: deltasignal_morning_brief, daily changes, daily-change evidence, company reports, pressure boards, alpha screens, and notification summaries all inherit the EDGAR source date boundary.
• The public documentation now treats EDGAR as the evidence substrate, with routes and rendered briefs only compiling returned evidence and preserving source dates, caveats, hashes, and non-advice boundaries.

Notification hardening and live verification checkpoint

The notification surface moved from coverage-chasing into hardening verification: production now confirms 215 active ATLAS-7 issuers, live field-contract aliases for MCP summaries and webhook delivery, live notification pricing metadata, and evidence-preserving daily-breakdown handles.

• Live readiness returned ok=true, distinct_issuer_count=215, source_date=2026-06-06, and a 36-hour freshness window.
• /v1/contract/fields now exposes compatibility aliases agentic_triggers.mcp_summary and agentic_triggers.webhook_delivery while preserving the earlier canonical names.
• /v1/notifications/summaries/mcp daily breakdown rows now carry evidence_refs and suggested_routes, and email digest rows render the same evidence handles.
• /v1/pricing advertises the MCP notification summary route at price_usd=0.18, credits_charged=18, billing_mode=x402, and cost_field=cost_usd.
• The background crawler now exposes a shutdown done channel and the gateway waits briefly for crawler loops before completing termination.
• Public boundary: this is a product-hardening checkpoint, not a personalized alert, private support note, or investment recommendation.

Consolidated June 6 public rollup to 76.4 percent coverage

The public changelog now includes the full June 6 public-safe update set through daily-change discovery/fallback coverage and DeltaSignal defensive store/help/readiness coverage at the verified 76.4% cmd/search-gateway package checkpoint.

• Rolls forward the 76.3% daily-change discovery/fallback checkpoint and the 76.4% defensive store/help/readiness checkpoint.
• Keeps notification and digest work current: MCP daily all-delta framing, Microsoft Graph email delivery, signed webhooks, terminal delivery, receipts, subscription preferences, and x402 notification pricing tiers remain documented.
• Keeps route-safety, pricing, field-contract, SPECTRA, ticker canonicalization, RSS/Atom feed, and LLM handoff updates in the public rollup.
• Keeps the public/private boundary intact: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

DeltaSignal defensive store/help/readiness coverage checkpoint

Defensive DeltaSignal coverage now verifies concrete DB close behavior, non-GET help route rejection, readiness filing-source blank and invalid-date guardrails, uninitialized blob-store fallback behavior, and existing override/nil-store behavior; the verified cmd/search-gateway package coverage checkpoint reached 76.4%.

• Covered concrete deltaSignalStore Close behavior with an initialized DB handle.
• Covered /help non-GET rejection while preserving existing public support route metadata.
• Covered readiness filing-source guardrails for blank dates, invalid dates, uninitialized blob-store lookups, nil-store fallback, and override trimming.
• Close and handleDeltaSignalHelp are now at 100%; resolveReadinessFilingSourceDate is at 93.3%.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

Consolidated June 6 public rollup to 76.3 percent coverage

The public changelog now includes the full June 6 public-safe update set through daily-change discovery/fallback coverage, readiness and CompanyFacts status helpers, daily movement loaders, route guards, notification digest polish, notification pricing/delivery ladder, and RSS/Atom subscriber feeds at the verified 76.3% cmd/search-gateway package checkpoint.

• Rolls forward public-safe notification and digest work: daily all-delta MCP notification framing, per-business-day grouping, ATLAS-7 universe matching, canonical tickers, workload statistics, routes, and non-advice boundaries.
• Rolls forward delivery and monetization surfaces: free event probes, Microsoft Graph email delivery, terminal delivery, signed webhooks, receipts, retry/dead-letter status, paid MCP summaries, and x402 notification pricing tiers.
• Rolls forward source-test hardening through readiness windows, market-regime helpers, CompanyFacts status helpers, daily-change movement loaders, daily-change discovery/fallback branches, route guards, OpenAPI payment helpers, Google News resolver branches, native-health RSS status, and compatibility helpers.
• Keeps the public/private boundary intact: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

Daily-change discovery and fallback coverage checkpoint

Daily-change discovery and fallback coverage now verifies crypto issuer discovery rows, missing discovery relation soft-unavailable behavior, scan and row-iteration errors, tracked-issuer summary variants, and synthesized daily-change fallback snapshots; the verified cmd/search-gateway package coverage checkpoint reached 76.3%.

• Covered loadDiscoveredCryptoIssuersForDate success, missing relation, non-missing query error, scan error, and row-iteration error branches.
• Covered summarizeTrackedIssuerDelta accession, filing-form, filing-date, default, and fallback wording branches.
• Covered loadLatestDailyChangesFallback success, empty result, sql.ErrNoRows, query-error, synthesized stats, and blob-store-unavailable freshness annotation behavior.
• This protects daily digest and MCP notification source semantics around new crypto issuer discovery and fallback daily-change evidence.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

Consolidated June 6 public rollup to 75.9 percent coverage

The public changelog now includes the full June 6 public-safe update set through notification digest polish, notification pricing/delivery ladder, OpenAPI payment helper coverage, Google News resolver coverage, native-health RSS coverage, compatibility result helper coverage, and DeltaSignal route guard coverage at the verified 75.9% cmd/search-gateway package checkpoint.

• Rolls forward public-safe notification work: daily all-delta digest framing, per-business-day grouping, ATLAS-7 universe matching, canonical ticker handling, workload statistics, evidence routes, delivery routes, manage-preferences routes, and non-advice boundaries.
• Rolls forward delivery and monetization surfaces: free event probes, Microsoft Graph email delivery, terminal delivery, signed webhooks, receipts, retry/dead-letter status, paid MCP summaries, and x402 notification pricing tiers.
• Rolls forward source-test hardening through OpenAPI payment helpers, Google News resolver branches, native-health RSS status, compatibility JSON-RPC helpers, warning normalization, and DeltaSignal route guard branches.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

Notification pricing and delivery ladder public rollup

The changelog now records notification pricing as a separate low-cost alert layer: event pings, ticker alerts, watchlist alerts, bundled workflow notifications, natural-language alert briefs, and PDF deliveries are distinct from full workflow reruns.

• Documents the public value ladder: low-cost raw alerts, mid-cost bundled workflow notifications, higher-cost natural-language briefs, and finished PDF deliverables.
• Keeps x402 notification prices separate from full workflow prices so alerts do not undercut Morning Brief, Natural Language, or finished-report products.
• Aligns paid MCP summaries, signed webhooks, terminal delivery, email delivery, delivery receipts, and subscription preferences under the same notification product boundary.
• Keeps the boundary explicit: notification outputs are evidence-routing and diligence triage, not buy/sell recommendations or personalized investment advice.

DeltaSignal route guard coverage checkpoint to 75.9 percent

DeltaSignal route guard coverage now verifies covenant-stress detail/list and raw top-stressed guard branches, including method rejection, authorization failures, validation errors, missing ticker handling, and unavailable-store responses; the verified cmd/search-gateway package coverage checkpoint reached 75.9%.

• Covered covenant-stress detail method rejection, missing ticker, invalid period, invalid source_date, and unavailable-store branches.
• Covered covenant-stress list and raw top-stressed method rejection, unauthorized request, and unavailable-store branches.
• The branch-level checkpoint reached handleDeltaSignalCovenantStressList at 100%, handleDeltaSignalTopStressed at 100%, and handleDeltaSignalCovenantStressDetail at 92%.
• This protects fail-closed route behavior for paid issuer stress and universe pressure surfaces.

Compatibility result helper coverage checkpoint

Compatibility result helper coverage now verifies JSON-RPC marshal fallback branches and warning-list normalization; the verified cmd/search-gateway package coverage checkpoint remained 75.8% after rounding.

• Covered buildMCPToolCallSuccessResult and buildMergedToolsListResponse marshal-fallback behavior with unmarshalable request IDs.
• Covered appendStringWarning behavior for string arrays, generic arrays, and unsupported existing warning payloads.
• This protects agent compatibility responses and merged MCP tool-list output from malformed or unusual runtime values.

Native health RSS status coverage checkpoint

Native health payload coverage now verifies the configured-but-unhealthy RSS index branch with Codex CLI status available; the verified cmd/search-gateway package coverage checkpoint remained 75.8% after rounding.

• Covered the RSS-index-down status path in buildNativeHealthPayload without requiring external service calls.
• Preserved explicit native-health reporting for configured sources, RSS index state, and Codex CLI readiness.
• This protects operator and integration health checks used around notification, crawl, and agent execution surfaces.

Google News resolver coverage checkpoint

Google News resolver coverage now verifies invalid-link fallback, redirect resolution, user-agent behavior, and stories-path fallback behavior; the verified cmd/search-gateway package coverage checkpoint reached 75.8%.

• Covered invalid Google News URL fallback behavior so malformed resolver inputs do not break crawling.
• Covered local redirect resolution through a deterministic HTTP test server and verified the resolver User-Agent.
• Covered stories-path behavior when no Location header is available.
• This protects background evidence-ingestion and news-link normalization used by downstream web-intelligence and notification surfaces.

OpenAPI payment helper coverage checkpoint

OpenAPI payment helper coverage now verifies Postgres DSN normalization, OpenAPI object cloning, payment amount coercion, and nested pricing metadata extraction; the verified cmd/search-gateway package coverage checkpoint reached 75.7%.

• Covered DSN empty, no-scheme, already-valid, missing-host, and missing-userinfo branches used by DeltaSignal store setup.
• Covered OpenAPI clone success, deep-copy behavior, marshal failure, and non-object failure branches.
• Covered payment amount coercion for float, integer, json.Number, dollar-string, invalid-string, unsupported, direct amount, nested price amount, and missing metadata paths.
• This protects public OpenAPI/x402 metadata without changing route prices or settlement semantics.

Daily all-delta MCP notification digest polish

The notification product is now documented as a Delta Signal MCP evidence-routing digest: after daily processing, recipients can receive per-source-date issuer deltas scoped to the full ATLAS-7 universe, with workload statistics, canonical tickers, routes, and non-advice boundaries.

• Reframes notification emails, terminal deliveries, webhooks, and paid MCP summaries as MCP evidence-routing alerts rather than newsletter or subscriber-media messages.
• Adds the daily all-deltas direction: show each business day separately, include all ATLAS-7 issuer matches, affected canonical tickers, candidate rows inspected, delivered rows, source dates, and available drilldowns.
• Keeps watchlists as an optional narrowing layer, while the default paid value is a universe-level daily evidence map after processing completes.
• Preserves public-safe language: no private recipient identifiers, wallet addresses, mailbox details, or design-partner support context.

Consolidated June 6 public rollup to 75.6 percent coverage

The public changelog now includes the full June 6 public-safe update set through SPECTRA dynamic helper coverage and MCP validation/coercion coverage, with RSS/Atom subscriber feeds and LLM handoff files synchronized to the verified cmd/search-gateway package coverage checkpoint at 75.6%.

• Rolls forward the public-safe notification work: free event discovery, Microsoft Graph email delivery, terminal delivery, signed webhooks, delivery receipts, retry/dead-letter status, durable subscriptions, paid MCP notification summaries, route pricing, and non-advice boundaries.
• Rolls forward Daily Delta Signal Digest behavior: source-date-separated business-day blocks, ATLAS-7 universe matches, affected tickers, evidence workload statistics, drilldown availability, and optional market context when available.
• Rolls forward ticker-quality work including ATLAS-7 universe filtering and canonical public ticker presentation, including warrant-to-common-stock display repair where the issuer evidence supports a primary common-share ticker.
• Rolls forward source-test hardening through SPECTRA field-map contract derivation, numeric/date/pressure helpers, MCP ticker and output-mode validation, common argument coercion, Daily Change Evidence validation, and composite workflow validation.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

MCP validation and coercion coverage checkpoint

DeltaSignal MCP validation and coercion coverage now verifies bounded defaults, integer coercion, common argument checks, ticker validation, output-mode validation, daily-change evidence checks, and composite workflow guardrails; the verified cmd/search-gateway package coverage checkpoint reached 75.6%.

• Covered boundedDefault and anyInt coercion paths used by MCP-facing route argument normalization.
• Covered common MCP argument validation, required ticker validation, composite output-mode validation, and direct tool validation branches.
• Covered Daily Change Evidence validation plus Morning Brief and no-argument composite workflow validation.
• This protects agent clients from ambiguous malformed requests while preserving route contracts, pricing behavior, and evidence boundaries.

SPECTRA dynamic helper coverage checkpoint

SPECTRA dynamic helper coverage now verifies field-map row normalization, scalar coercion, point-date bounds, min/max normalization, compression/release labels, pressure/fair-value reads, rounding, and historical contract derivation; the verified cmd/search-gateway package coverage checkpoint reached 75.4%.

• Covered SPECTRA numeric, string, and boolean coercion helpers plus empty/dateless contract rejection paths.
• Covered SPECTRA point-range and normalization behavior used to build dynamic field-map contracts from ATLAS-history-shaped rows.
• Covered compression, release, pressure, and fair-value label derivation so field-map summaries remain stable for agent and UI readers.
• This protects SPECTRA contract generation without changing public evidence semantics or expanding investment-advice behavior.

Consolidated June 6 public rollup to 75.2 percent coverage

The public changelog now includes the full June 6 public-safe update set through DeltaSignal helper branches and HTTP handler guard coverage, with RSS/Atom subscriber feeds and LLM handoff files synchronized to the verified cmd/search-gateway package coverage checkpoint at 75.2%.

• Rolls forward the public-safe notification work: free event discovery, Microsoft Graph email delivery, terminal delivery, signed webhooks, delivery receipts, retry/dead-letter status, durable subscriptions, paid MCP notification summaries, route pricing, and non-advice boundaries.
• Rolls forward Daily Delta Signal Digest behavior: source-date-separated business-day blocks, ATLAS-7 universe matches, affected tickers, evidence workload statistics, drilldown availability, and optional market context when available.
• Rolls forward ticker-quality work including ATLAS-7 universe filtering and canonical public ticker presentation, including warrant-to-common-stock display repair where the issuer evidence supports a primary common-share ticker.
• Rolls forward source-test hardening through DeltaSignal natural-style normalization, row/ticker/value helpers, token and date helpers, readiness health payload branches, and method/auth/validation/store-unavailable HTTP handler guards.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

DeltaSignal handler and helper guard coverage checkpoint

DeltaSignal helper and handler guard coverage now verifies small helper branches, native health readiness reporting, and fail-closed HTTP behavior; the verified cmd/search-gateway package coverage checkpoint reached 75.2%.

• Covered DeltaSignal natural-style normalization, first-row extraction, first publishable ticker selection, generic string conversion, rough token counting, clamp/bool helpers, and offset date formatting.
• Covered native health readiness payload behavior for configured Web Intel sources and available Codex CLI status.
• Covered method guards, unauthorized requests, validation errors, and unavailable-store responses across readiness, daily changes, daily-change evidence, peer ranking, top-stressed natural, Morning Brief natural, and covenant-stress natural routes.
• This protects public route safety and agent-facing failure semantics without changing route prices, evidence payload meaning, or billing behavior.

Consolidated June 6 public rollup to 74.9 percent coverage

The public changelog now includes the full June 6 public-safe update set through worker-proxy and DeltaSignal store-constructor coverage, with RSS/Atom subscriber feeds and LLM handoff files synchronized to the verified cmd/search-gateway package coverage checkpoint at 74.9%.

• Rolls forward the public-safe notification work: free event discovery, Microsoft Graph email delivery, terminal delivery, signed webhooks, delivery receipts, retry/dead-letter status, durable subscriptions, paid MCP notification summaries, route pricing, and non-advice boundaries.
• Rolls forward Daily Delta Signal Digest behavior: source-date-separated business-day blocks, ATLAS-7 universe matches, affected tickers, evidence workload statistics, drilldown availability, and optional market context when available.
• Rolls forward source-test hardening through Codex compatibility handlers, process-runner branches, dynamic crawler loops, worker proxy forwarding/error paths, response-header copying, and DeltaSignal store constructor fallback branches.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

Worker proxy and DeltaSignal store constructor coverage checkpoint

Worker proxy and store-constructor coverage now verifies authorized proxy forwarding with query/body/header preservation, transport-error behavior, proxy response-header filtering, OpenAPI template fallback loading, and no-op DeltaSignal store close behavior; the verified cmd/search-gateway package coverage checkpoint reached 74.9%.

• Covered worker proxy path forwarding and error handling without changing public route behavior.
• Covered response-header copy rules so proxied responses do not preserve stale Content-Length values and do replace existing destination header values.
• Covered DeltaSignal store initialization when no Postgres DSN is configured, including embedded OpenAPI template loading and close behavior.
• This protects backend proxy and startup fallback paths used by agent-facing web-intelligence and DeltaSignal API surfaces.

Consolidated June 6 public rollup to 74.7 percent coverage

The public changelog now includes the full June 6 public-safe update set through Codex compatibility-handler coverage, with RSS/Atom subscriber feeds and LLM handoff files synchronized to the verified cmd/search-gateway package coverage checkpoint at 74.7%.

• Rolls forward the public-safe notification work: free event discovery, Microsoft Graph email delivery, terminal delivery, signed webhooks, delivery receipts, retry/dead-letter status, durable subscriptions, paid MCP notification summaries, route pricing, and non-advice boundaries.
• Rolls forward the Daily Delta Signal Digest direction: after daily processing, group each source date separately, include ATLAS-7 universe matches, evidence workload statistics, affected tickers, drilldown availability, and optional market context when available.
• Rolls forward source-test hardening through Codex HTTP handler guardrails, compatibility tool-call normalization, local MCP validation branches, JSON-result fallback behavior, Codex process-runner branches, and dynamic crawler loop coverage.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

Codex compatibility handler coverage checkpoint

Codex compatibility-handler coverage now verifies auth and bad-JSON paths for Codex HTTP handlers, no-op and error branches in compatibility tool-call normalization, local MCP validation branches, and JSON-result fallback behavior; the verified cmd/search-gateway package coverage checkpoint reached 74.7%.

• Covered Codex HTTP auth and malformed JSON paths for web research and execution routes.
• Covered compatibility tool-call normalization no-op and error branches, local MCP tool-call validation branches, and MCP tool-call JSON result fallback behavior.
• This protects the Codex-facing compatibility surface used by agents that bridge local MCP calls, web-research calls, and structured tool-call responses.

Consolidated June 6 public rollup to 74.4 percent coverage

The public changelog now includes the full June 6 public-safe update set through notification delivery, daily all-delta digest framing, x402 notification pricing, RSS/Atom subscriber feeds, Codex process-runner coverage, dynamic crawler loop coverage, and the verified cmd/search-gateway package coverage checkpoint at 74.4%.

• Rolls forward the public-safe notification work: free event discovery, Microsoft Graph email delivery, terminal delivery, signed webhooks, delivery receipts, retry/dead-letter status, durable subscriptions, paid MCP notification summaries, route pricing, and non-advice boundaries.
• Records the Daily Delta Signal Digest direction as an MCP evidence-routing product: after daily processing, group each source date separately, include ATLAS-7 universe matches, evidence workload statistics, affected tickers, drilldown availability, and optional market context when available.
• Rolls forward source-test hardening through Codex process-runner branches and the dynamic crawler loop after the risk-distribution and MCP composite-wrapper checkpoints.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

Dynamic crawler loop coverage checkpoint

Dynamic feed-crawler coverage now verifies source-listing success and error paths, empty dynamic source sets, file-feed filtering, local dynamic RSS fetches, and canceled loop shutdown; the verified cmd/search-gateway package coverage checkpoint reached 74.4%.

• Introduced a narrow dynamic feed-source lister seam so crawler behavior can be regression-tested without changing production route semantics.
• Covered dynamicCrawlOnce, dynamicCrawlerLoop, and crawlOnce behavior for dynamic source success, source-listing failure, empty results, file-feed skip behavior, HTTP RSS fetch behavior, and context cancellation.
• This protects the background evidence-ingestion surface that feeds downstream notification, discovery, and web-intelligence workflows.

Codex process-runner coverage checkpoint

Codex process-runner coverage now verifies stdout/stderr callbacks, output caps, nonzero exits, context timeout behavior, and missing executable handling; the verified cmd/search-gateway package coverage checkpoint reached 74.2%.

• Added deterministic local executable tests for runCodexProcess so process lifecycle behavior is covered without invoking an external Codex binary.
• Covered successful stdout/stderr streaming, callback aggregation, bounded output capture, nonzero exit propagation, context cancellation, and lookup failure handling.
• This protects the gateway runtime path used by Codex-backed web-research and execution routes.

Notification digest, delivery, and x402 pricing rollup

The notification surface is now documented as a Delta Signal MCP evidence-routing layer, not subscriber media: free metadata events, paid MCP summaries, signed webhooks, terminal and email delivery, business-day daily digests, route receipts, subscription preferences, and low-cost x402 notification pricing tiers.

• Frames every notification as an MCP evidence-routing alert with evidence route, delivery route, manage-preferences route, source dates, affected tickers, and non-advice boundary.
• Documents the daily all-deltas digest direction: full ATLAS-7 universe filtering after processing, per-day grouping for five business days, workload statistics, candidate rows, matched tickers, delivered rows, and drilldown availability.
• Records launch pricing guidance for notification-layer products: raw service/daily events, ticker alerts, watchlist alerts, bundled workflow notifications, natural-language alert briefs, and finished PDF delivery as separate x402-priced layers.
• Keeps notification pricing below full workflow reruns while preserving the value ladder for Morning Briefs, Natural Language briefs, and finished reports.

Consolidated June 6 public rollup to 73.9 percent coverage

The public changelog now includes the full June 6 public-safe update set through risk-distribution and MCP composite-wrapper coverage hardening, with RSS/Atom subscriber feeds and LLM handoff files synchronized to the 73.9% coverage checkpoint.

• Rolls forward the complete public-safe June 6 update stream across notification-v1, email delivery, signed webhooks, terminal delivery, paid MCP notification summaries, subscriptions, delivery receipts, x402 notification pricing, business-day digests, ATLAS-7 universe filtering, ticker canonicalization, RSS/Atom changelog feeds, and LLM handoff updates.
• Rolls forward source-test hardening through risk distribution and MCP composite wrappers after alpha routes/loaders, ATLAS-7 history, dedicated grant ledger, SignalRadar MCP, StrategiX Diagram MCP, MCP summary, billing-envelope, company-fundamentals, primitive, Codex cache, Web Intel, Telegram, Marketplace, OPML, static runtime, generic MCP, and field-map coverage slices.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

DeltaSignal MCP composite wrapper coverage checkpoint

MCP composite wrapper coverage now verifies fail-closed behavior for Company Report, Issuer Deep Report, Pressure Board, Alpha Sweep, Quick Ticker Check, and Daily Change Evidence wrappers; the verified cmd/search-gateway package coverage checkpoint reached 73.9%.

• Covered MCP composite server wrappers so agent-facing workflow calls fail closed through structured errors when the HTTP caller/store path is unavailable.
• Covered Daily Change Evidence MCP tool-call branches for invalid arguments, store-not-configured paths, and unavailable loader behavior.
• This protects the Track 3 agent-native surface where MCP clients discover, select, and execute bounded workflows without losing evidence boundaries or route provenance.

Risk distribution route and loader coverage checkpoint

Risk-distribution route coverage now verifies handler success, guardrails, loader error branches, and unavailable-store behavior; the verified cmd/search-gateway package coverage checkpoint reached 73.3%.

• Covered the risk-distribution handler for successful response rendering, method/auth guardrails, store-unavailable behavior, and structured route envelope behavior.
• Covered risk-distribution loader branches for successful rows, missing/empty state, query error propagation, and JSON shaping so universe-level risk screens remain regression-protected.
• The active 100% package coverage goal remains open; this entry is source-test hardening, not a final coverage claim.

Consolidated June 6 public rollup to 73.2 percent coverage

The public changelog now includes the full June 6 public-safe update set through the alpha route/loaders coverage slice, with RSS/Atom subscriber feeds and LLM handoff files synchronized to the 73.2% coverage checkpoint.

• Rolls forward the complete public-safe June 6 update stream across notification-v1, email delivery, signed webhooks, terminal delivery, paid MCP notification summaries, subscriptions, delivery receipts, x402 notification pricing, business-day digests, ATLAS-7 universe filtering, ticker canonicalization, RSS/Atom changelog feeds, and LLM handoff updates.
• Rolls forward source-test hardening through alpha signals, alpha opportunities, alpha audit, alpha universe, opportunity-window loaders, and alpha route handler branches after the ATLAS-7 history, dedicated grant ledger, SignalRadar MCP, StrategiX Diagram MCP, MCP summary, billing-envelope, company-fundamentals, primitive, Codex cache, Web Intel, Telegram, Marketplace, OPML, static runtime, generic MCP, and field-map coverage slices.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

Alpha routes and loader coverage checkpoint

Alpha route and loader coverage now verifies alpha-signals, alpha-opportunities, alpha audit, alpha universe, source-date resolution, window leaders, and query-error behavior; the verified cmd/search-gateway package coverage checkpoint reached 73.2%.

• Covered alpha-signals, alpha-opportunities, and alpha-opportunities audit handlers for method guards, auth guards, validation, successful JSON responses, and route-envelope behavior.
• Covered SQL-backed alpha loaders for alpha-signal success and missing rows, alpha-opportunity validation and success, blank and populated opportunity-window loaders, window-leader JSON shaping, alpha-universe selection, source-date resolution, and query error propagation.
• The active 100% package coverage goal remains open; this entry is source-test hardening, not a final coverage claim.

Consolidated June 6 public rollup to 72.5 percent coverage

The public changelog now includes the full June 6 public-safe update set through the ATLAS-7 history route/loaders coverage slice, with RSS/Atom subscriber feeds and LLM handoff files synchronized to the 72.5% coverage checkpoint.

• Rolls forward the full public-safe June 6 update set across notification-v1, Graph email delivery, daily all-delta digests, x402 notification pricing, signed webhooks, terminal delivery, paid MCP summaries, subscriptions, delivery receipts, RSS/Atom changelog feeds, and periodic changelog synchronization.
• Rolls forward source-test hardening through ATLAS-7 calculation-history and point-in-time-history routes, after dedicated grant ledger, SignalRadar MCP, StrategiX Diagram MCP, MCP summary, billing-envelope, company-fundamentals, primitive, Codex cache, Web Intel, Telegram, Marketplace, OPML, static runtime, generic MCP, and field-map coverage slices.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

ATLAS-7 history route and loader coverage checkpoint

ATLAS-7 calculation-history and point-in-time-history route coverage now verifies handlers, loader branches, source-date resolution, row helpers, scalar/hash extraction, nullable helpers, and query-error behavior; the verified cmd/search-gateway package coverage checkpoint reached 72.5%.

• Covered calculation-history and point-in-time-history handlers for method guards, auth guards, validation, loader success, JSON response shape, and source-date resolution paths.
• Covered SQL loader and row-shaping helpers for calculation-history rows, scalar and hash extraction, point-in-time history rows, nullable float/bool helpers, missing-source behavior, and query error propagation.
• The active 100% package coverage goal remains open; this entry is source-test hardening, not a final coverage claim.

Consolidated June 6 public rollup to 71.8 percent coverage

The public changelog now includes the full June 6 public-safe update set through the dedicated grant ledger coverage slice, with RSS/Atom subscriber feeds and LLM handoff files synchronized to the 71.8% coverage checkpoint.

• Rolls forward the public-safe June 6 change stream across notification-v1, Graph email delivery, daily all-delta digests, x402 notification pricing, signed webhooks, terminal delivery, paid MCP summaries, subscriptions, delivery receipts, RSS/Atom changelog feeds, and periodic changelog synchronization.
• Rolls forward source-test hardening through the dedicated grant ledger, after SignalRadar MCP, StrategiX Diagram MCP, MCP summary, billing-envelope, company-fundamentals, primitive, Codex cache, Web Intel, Telegram, Marketplace, OPML, static runtime, generic MCP, and field-map coverage slices.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

Dedicated grant ledger coverage checkpoint

SQL-backed dedicated grant ledger coverage now verifies grant seeding, wallet identity mapping, consumption, exhaustion, usage reporting, query error propagation, and close paths; the verified cmd/search-gateway package coverage checkpoint reached 71.8%.

• Covered the Postgres-backed dedicated grant ledger path for ensure/seed behavior, empty DSN guardrails, grant lookup, grant consumption, missing-wallet handling, exhausted-grant handling, wallet identity mapping, and wallet fallback behavior.
• Covered usage reporting, recent usage reads, direct query helper scanning, query error propagation, and close/nil branches so grant-backed zero-balance execution remains regression-protected without exposing private wallet identities.
• The verified cmd/search-gateway package coverage checkpoint reached 71.8%; the active 100% package coverage goal remains open.

Consolidated June 6 public rollup to 70.7 percent coverage

The public changelog now includes the full June 6 public-safe update set through SignalRadar MCP and StrategiX Diagram MCP coverage hardening, with the latest verified cmd/search-gateway package coverage checkpoint at 70.7%.

• Rolls forward the public-safe June 6 change stream across notification-v1, Graph email delivery, daily all-delta digests, x402 notification pricing, signed webhooks, terminal delivery, paid MCP summaries, subscriptions, receipts, and RSS/Atom changelog feeds.
• Adds the latest MCP source-test hardening checkpoints for SignalRadar MCP handlers and StrategiX Diagram MCP helpers, after the previously recorded MCP summary, billing-envelope, company-fundamentals, primitive, Codex cache, Web Intel, Telegram, Marketplace, OPML, static runtime, generic MCP, and field-map coverage slices.
• Preserves the public/private boundary: no individual design-partner names, mailbox details, wallet addresses, private credit amounts, secrets, or private support artifacts are included.
• The active 100% package coverage goal remains open; this entry is a dated checkpoint, not a final coverage claim.

StrategiX Diagram MCP helper coverage checkpoint

StrategiX Diagram MCP coverage now verifies tool definitions, call-dispatcher success and error paths, validation warnings and errors, render/package/search text helpers, compact metadata fallback, fit-fail reporting, pricing fallback, hash fallback, label shortening, and primitive helper branches.

• Covered StrategiX Diagram MCP validate, render, package, and search tool definitions plus dispatcher success and malformed/unsupported-tool error branches.
• Covered validation errors and warnings for duplicate IDs, missing labels, missing edge endpoints, missing referenced nodes, missing aspect and height constraints, and rendered-height fit failures.
• Covered deterministic render/package/search text helpers, compact metadata fallback, pricing fallback, hash fallback, label shortening, first-positive/max-float fallbacks, and compact-string behavior.
• The verified cmd/search-gateway package coverage checkpoint reached 70.7%; the active 100% package coverage goal remains open.

SignalRadar MCP handler coverage checkpoint

SignalRadar MCP handler coverage now verifies tool discovery, tool recognition, stateless evidence/friction/repo-scan routing, store-not-configured errors, SQL-backed observation/list/match/session/action success paths, validation errors, and nil-store failures.

• Covered SignalRadar MCP tool definitions, tool-name recognition, stateless evidence map generation, friction simulation, and repository scan routing.
• Covered SQL-backed SignalRadar observation recording, opportunity listing, opportunity matching, session recording, and action recording success paths.
• Covered store-not-configured errors, validation errors, and nil-store failures so MCP clients get structured errors instead of ambiguous failures.
• The verified cmd/search-gateway package coverage checkpoint reached 70.4%; the active 100% package coverage goal remains open.

DeltaSignal MCP summary helper coverage checkpoint

DeltaSignal MCP summary helper coverage now verifies evidence-time parsing, compact JSON generation, date-prefix handling, payload compaction detection, summary construction, numeric coercion, first-number extraction, suggested follow-up generation, and summary clamping.

• Covered parseDeltaSignalEvidenceTime, compactJSONString, datePrefix, deltaSignalMCPPayloadIsCompacted, deltaSignalMCPSummary, deltaSignalMCPFloatFromAny, deltaSignalMCPNumberFromAny, deltaSignalMCPFirstNumberAt, deltaSignalMCPSuggestedFollowUps, and clampDeltaSignalMCPSummary helper behavior.
• Protected the MCP-facing summary envelope used by agent-readable notifications, compact evidence rendering, and route-response summaries without changing billing, route prices, or evidence semantics.
• The verified cmd/search-gateway package coverage checkpoint reached 70.0%; the active 100% package coverage goal remains open.

Consolidated June 6 public rollup to 69.5 percent coverage

The public changelog now includes the full June 6 public-safe update set across notification-v1, daily digest behavior, billing, delivery channels, ATLAS-7/SPECTRA coverage, ticker canonicalization, feeds, route contracts, and coverage hardening through 69.5%.

• Rolls up notification channels, daily all-delta digest behavior, Microsoft Graph email delivery, x402 notification pricing, signed webhooks, terminal delivery, paid MCP summaries, durable subscriptions, delivery receipts, and changelog RSS/Atom feeds.
• Rolls up SPECTRA and ATLAS-7 hardening: live ATLAS-history SPECTRA primary behavior, field-map route coverage, ticker canonicalization, route-contract stability, universe-scoped daily-change filtering, and evidence-preserving digest metadata.
• Rolls up source-test coverage checkpoints through 69.5% package coverage while preserving the open 100% coverage goal and avoiding private support identifiers.

Billing envelope primitive helper coverage checkpoint

Billing-envelope primitive helper coverage now verifies nullable booleans, nullable arrays, nested-string extraction, and billing response-writer header/body behavior.

• Covered nullable billing helper branches for nil, typed, coercion, and fallback paths.
• Covered billing response writer header and body paths so route-level cost and settlement metadata remain regression-protected.
• The verified cmd/search-gateway package coverage checkpoint reached 69.5%; the active 100% package coverage goal remains open.

Company fundamentals metadata helper coverage checkpoint

Company-fundamentals metadata helper coverage now verifies CIK normalization, linkbase-backed state, data-source classification, and quality-flag derivation.

• Covered normalized CIK strings, linkbase-backed state, data-source classification, and quality-flag derivation branches.
• Protected issuer fundamentals metadata used by company-fundamentals, company-report, MCP summaries, daily digests, and parser-stable evidence envelopes.
• The verified cmd/search-gateway package coverage checkpoint reached 69.5%; the active 100% package coverage goal remains open.

Periodic changelog and subscriber feed sync policy

The public documentation set now treats changelog.html, changelog-llm.html, rss.xml, atom.xml, llms.txt, and llms-full.txt as synchronized release surfaces for recurring product updates.

• RSS and Atom links remain exposed from the human changelog, LLM changelog, and landing page for subscribers who need periodic update tracking.
• The feed generator reads the LLM changelog contract, so new public entries propagate into both subscriber feeds with stable tripcodes and breadcrumbs.
• Private support context stays out of the public changelog; entries describe generalized product, contract, delivery, billing, MCP, SPECTRA, and coverage changes.

DeltaSignal primitive helper coverage checkpoint

DeltaSignal primitive parsing and ticker helper coverage now verifies bounded integers, optional floats and booleans, nullable numbers and JSON arrays, ticker display/resolution helpers, and generic integer/bool coercion.

• Covered parseBoundedInt, parseOptionalFloat, parseOptionalBool, parseNullableNumber, parseNullableFloat64, nullIfFalseFloat64, parseNullableJSONArray, nullInt, intFromAny, int64FromAny, anyBool, and tickerOr helper branches.
• Covered deltaSignalTickerDisplay, deltaSignalResolvedTicker, and deltaSignalTickerResolutionStatus so canonical ticker presentation stays stable for route envelopes and digest surfaces.
• The verified cmd/search-gateway package coverage checkpoint reached 69.4%; this is still in-progress coverage hardening toward the open 100% package goal.

Codex cache helper coverage checkpoint

Codex cache and runtime helper coverage now verifies default cache-skip configuration, dynamic-search skip decisions, runtime path handling, cache metadata normalization, and deterministic helper branches.

• Covered DefaultCacheSkipConfig and ShouldSkipDynamicSearch so cache-bypass behavior remains explicit and regression-protected.
• Covered Codex runtime helper branches for metadata parsing, cache records, path handling, and deterministic response helpers without calling external services.
• The verified cmd/search-gateway package coverage checkpoint reached 69.3%; the active 100% coverage goal remains open.

Subscriber changelog feeds and public rollup maintenance

The public changelog now explicitly tracks RSS and Atom subscriber feeds as first-class update surfaces for notification, billing, coverage, MCP, SPECTRA, and route-contract changes.

• Updated the human and LLM changelog surfaces with the latest public rollup while keeping private design-partner identifiers out of the public artifact.
• Regenerated RSS and Atom feeds from the LLM contract so subscribers can follow the changelog without manually reopening the site.
• Preserved the evidence boundary: changelog entries describe product and contract changes, not private support context or personalized financial advice.

Web Intel and Telegram helper coverage checkpoint

Committed Web Intel and Telegram helper coverage now verifies deterministic result helpers, Telegram bridge helpers, cache keys, authorization checks, approval formatting, and response rendering.

• Web Intel helper coverage now exercises deterministic result ordering, canonical link handling, fetched-item dedupe, summary generation, and hot-cache key construction.
• Telegram helper coverage now exercises configuration parsing, webhook validation, allowed-user checks, approval actor authorization, text rendering, pending-approval formatting, compact command execution arguments, and response formatting.
• The verified package coverage checkpoint reached 69.1%; this remains a coverage-hardening checkpoint, not a claim that the broader 100% coverage goal is complete.

Microsoft Marketplace client helper coverage checkpoint

Microsoft Marketplace SaaS helper coverage now verifies client response handling, webhook secret validation, subscription provisioning, webhook action mapping, tier extraction, and marketplace string helpers.

• ResolveSubscription, GetOperation, response decoding, marketplace app selection, webhook handling, provisioning, and action/status helpers are covered at 100% for the targeted helper slice.
• The committed package coverage checkpoint advanced to 68.3% after this marketplace coverage slice.
• This is billing and marketplace integration hardening only; it does not change notification evidence semantics, x402 settlement rules, or free discovery behavior.

OPML feed helper coverage checkpoint

OPML feed helper coverage now verifies feed collection helpers, source ID derivation, source domain derivation, ID sanitation, and handler guard paths.

• Added deterministic tests for malformed import bodies, unsupported methods, empty export behavior, and feed helper edge cases.
• The latest verified cmd/search-gateway package coverage checkpoint is 67.7%; the active 100% coverage goal remains open.
• Storage-backed OPML success paths remain a separate target because they require the concrete Postgres feed-source index rather than the pure helper layer.

StrategiX web static runtime coverage checkpoint

StrategiX web static runtime coverage now verifies constructor, host matching, index serving, asset serving, SPA fallback, missing assets, and root handler dispatch.

• Covered host normalization and local static routing branches so the public landing/docs runtime stays regression-protected.
• The package coverage checkpoint advanced to 67.5% at this slice before the OPML feed helper checkpoint raised it to 67.7%.
• This is source coverage hardening only; it does not change public route semantics.

ATLAS and SPECTRA field-map route coverage checkpoint

ATLAS/SPECTRA field-map handler coverage now verifies validation, not-found semantics, JSON contract serving, v1 SPECTRA dispatch, environment override resolution, glob fallback, and latest-contract selection.

• Covered ATLAS and SPECTRA field-map validation for method-not-allowed, missing ticker, invalid ticker, and structured not-found behavior.
• Covered JSON contract serving from local ATLAS and SPECTRA field-map directories, including the /v1/spectra-field-map/{ticker} route path.
• Covered environment override lookup, multi-directory fallback, globbed contract directories, and latest-modified contract selection.
• The latest verified cmd/search-gateway package coverage checkpoint is 67.3%; the active 100% coverage goal remains open.

Generic MCP server helper coverage checkpoint

Generic MCP helper coverage now exercises result wrappers, auth middleware, streamable handler construction, and tool-adapter validation/error branches.

• Covered textResult, errResult, and mcpAuthMiddleware at 100% for API-key, Bearer-token, disabled-auth, and overload rejection paths.
• Added deterministic validation/error coverage for search, lookup, browse, and sources tool adapters without invoking external web services.
• Covered MCP server and streamable handler construction branches so public MCP discovery and tool-envelope plumbing remain regression-protected.
• The package coverage checkpoint advanced to 67.2%; remaining low-coverage areas still include dynamic crawler loops, live process execution, and storage-backed runtime paths.

DeltaSignal web static runtime coverage checkpoint

DeltaSignal web static runtime coverage now exercises constructor, disabled/nil runtime, method rejection, SPA fallback, asset serving, missing-asset, static path cleaning, and gateway-reserved path branches.

• Added deterministic tests for the DeltaSignal static web runtime constructor, enabled/disabled branches, nil runtime behavior, and static asset dispatch.
• Covered method rejection, missing assets, SPA fallback behavior, path extension detection, static request path cleaning, and gateway-reserved path handling.
• The package coverage checkpoint advanced to 66.7%; this is still a work-in-progress checkpoint toward full gateway coverage, not a final 100% claim.
• This is source coverage hardening only; it does not change public route semantics.

Free-tier, helper, and route-safety coverage advanced to 66.6 percent

The active coverage-hardening plan now records Web Intel helper coverage, native health/boolean normalization branches, free-tier admin handler branches, constructor metadata/time parsing, and a reserved-route safety fix.

• Added coverage for Web Intel source filtering, Codex helper behavior, boolean normalization, native health fallback/down branches, and short-string truncation safety.
• Added coverage for Delta Signal free-tier constructor metadata, optional time parsing, admin credit/usage handlers, and admin error branches.
• Reserved latest as a route segment in free-tier ticker extraction so /v1/daily-changes/latest remains universe-scoped and is not logged as ticker LATEST.
• Latest verified cmd/search-gateway package coverage is 66.6%; this remains a work-in-progress coverage checkpoint, not a final 100% claim.

Public rollup for notifications, coverage, SPECTRA, grants, and changelog feeds

Public changelog rollup now records the recent notification, SPECTRA, wallet-grant, parser-contract, digest, feed, and coverage-hardening work without private design-partner details.

• Notification-v1 is captured as an MCP evidence-routing layer with free event discovery, signed webhooks, terminal delivery, Microsoft Graph email delivery, delivery receipts, retry/dead-letter status, durable subscriptions, and paid MCP summaries.
• The Daily Delta Signal Digest framing is recorded as the default notification product direction: all ATLAS-7 matched issuer deltas after daily processing, grouped by source date, with five-business-day rollups and evidence workload statistics.
• The x402 notification price ladder is documented separately from full workflow reruns: low-cost raw event alerts, ticker/watchlist alerts, workflow notifications, natural-language alert briefs, and finished PDF deliverables.
• ATLAS-7 issuer coverage and SPECTRA status are recorded publicly: 215-row universe verification, runtime ATLAS-history SPECTRA primary behavior, watchlist route checks, and ticker canonicalization including FLD as Fold Holdings common stock.
• Wallet-grant and zero-balance access lessons are preserved as public-safe architecture notes: signed wallet grant matching, DB-backed grant counters, canonical cost fields, and no exposure of individual names, email addresses, wallet addresses, grant amounts, or private settlement proofs.
• Parser and integrator contracts remain explicit: path-ticker-free universe routes, structured not-found behavior, response metadata envelopes, /v1/pricing, /v1/contract/fields, large-response guidance, and terminal broker envelope keys.
• Changelog operations now include human and LLM changelog surfaces plus RSS and Atom subscriber feeds generated from the machine-readable changelog contract.
• Coverage hardening remains active, not complete: latest recorded backend package coverage is 67.7%, with additional helper-branch tests in progress and the 100% goal still open.

Coverage hardening advanced to 65 percent package coverage

The ongoing 100% coverage goal advanced from the earlier recorded 64.2% checkpoint to a verified 65.0% package coverage checkpoint for cmd/search-gateway.

• Added coverage for ATLAS-7 history helper paths, DeltaSignal helper paths, compatibility helpers, articles sync handler, Codex runtime coverage, crawler hardening, rolling brief helpers, thesis readiness helpers, morning brief issuer helpers, and public daily brief handler paths.
• Latest verified focused slices include public daily brief MCP response wrapping, method/auth/format behavior, morning-brief issuer selection/dedupe/drilldown helpers, and rolling brief normalization.
• The coverage goal remains active; this is not a final 100% coverage claim.
• Verification continues to use Go tests, coverage profiles, secret scan, whitespace checks, and ExecPlan HTML/XML validation.

Notification channel matrix and acceptance harness

The notification product surface is recorded as a channel matrix: free pull feed, signed webhooks, terminal delivery, email delivery, paid MCP summaries, receipts/status lookup, and subscription preferences.

• Added notification delivery channels and expanded the partner acceptance harness for end-to-end delivery verification.
• Recorded the notification acceptance packet with public-safe requirements for no-polling delivery, receipts, retries, pricing disclosure, and non-advice boundaries.
• Kept signed webhook delivery as the core no-polling integration substrate, with terminal and email treated as convenience delivery channels.
• Maintained separation between raw free event discovery and paid interpretation or delivery products.

Notification x402 price ladder and contract verification

Notification pricing is recorded as a separate low-cost alert layer with route-level x402 metadata, preserving higher prices for composed natural-language briefs and finished deliverables.

• Added the notification x402 price ladder: low-cost event alerts, ticker-level alerts, bundled workflow notifications, natural-language alert briefs, and finished PDF delivery tiers.
• Aligned notification contract verification around route_uri, billing_mode, payment_status, billing_status, cost_usd, quoted_cost_usd, actual_cost_usd, credits metadata, and request_id.
• Hardened remaining notification integration gaps so public discovery, pricing metadata, delivery contracts, and test coverage stay aligned.
• This changelog entry records route-contract and test hardening; it does not expose private settlement proofs or customer billing details.

Notification delivery edge coverage hardened

Notification test coverage expanded across universe loading, terminal failure paths, subscription persistence, email handler errors, event feed pagination, webhook receipt persistence, delivery edge paths, and notification summary edge cases.

• Covered notification universe-index loading and fallback behavior.
• Covered terminal delivery failure paths, receipt persistence, and cursor-safe response behavior.
• Covered email sender and handler errors without relying on live credentials in tests.
• Covered webhook delivery and receipt failure paths, plus event feed pagination and stored summary loading edge cases.

Business-day daily digest rollout

Daily notification digest rendering now supports source-date grouping and five-business-day rollups so recipients can review each processing day separately instead of receiving one undifferentiated alert.

• Added a business-day selector for notification digests and rendered each source date as its own section.
• Expanded email rendering so the latest day and the prior five business days can be delivered as a separated digest view.
• Preserved daily evidence workload metrics per section: changed companies, fact changes, changed/new files, raw bytes, candidate rows, ATLAS-7 universe matches, delivered rows, and drilldown availability.
• Recorded the rollout as MCP notification infrastructure, not subscriber media or investment advice.

Outlook and Microsoft Graph email delivery verified

Notification email delivery now has both an Outlook SMTP path and a Microsoft Graph path recorded, with Graph used as the production-grade authenticated delivery channel for Delta Signal MCP notifications.

• Added Outlook SMTP delivery support and documented the authentication blocker caused by tenant consent and shell-special password characters during operator setup.
• Added Microsoft Graph notification delivery support and verified a real Graph delivery probe from the configured organization mailbox.
• Recorded Graph email delivery verification without exposing the mailbox password, OAuth tokens, tenant secret material, or private recipient details.
• Email notifications keep the MCP evidence-routing framing, source route, delivery route, manage-preferences route, and non-advice boundary.

Notification channels, paid summaries, subscriptions, and daily digest rollout

Notification-v1 is now recorded as a multi-channel MCP evidence-routing layer with free event discovery, paid summaries, delivery transports, subscriptions, receipts, pricing, and daily digest framing.

• Free discovery remains available through GET /v1/events/latest with metadata-only events, schema version, cost metadata, and non-advice boundary language.
• Email delivery, terminal delivery, signed webhook delivery, delivery receipts, retry/dead-letter status, and durable subscription preferences are documented as production notification paths.
• POST /v1/notifications/summaries/mcp is recorded as the paid agent-readable notification-summary path with x402 billing metadata and route pricing in the public discovery surface.
• The launch pricing ladder distinguishes low-cost event alerts, bundled workflow notifications, natural-language alert briefs, and finished PDF deliverables.
• The product framing moved from narrow watchlist alerting to a Daily Delta Signal Digest: all ATLAS-7 matched issuer deltas after processing, evidence workload stats, ticker context where available, BTC/ATLAS backdrop, drilldown links, and manage-preferences links.
• Public changelog wording omits private design-partner names, wallet addresses, email addresses, and grant amounts while preserving the real integration lessons.

Changelog feed automation and coverage-hardening rollup

The public changelog now has subscriber feeds and a consolidated rollup of the ongoing coverage-hardening work, without private design-partner names or local operator details.

• Added RSS and Atom discovery links to the human and LLM changelog surfaces, plus a generator and GitHub Actions checks so feed files stay aligned with dated changelog entries.
• Recorded deterministic coverage-hardening progress across EDGAR index helpers, CompanyFacts daily-delta digest helpers, MCP helper paths, public report helpers, report-row helpers, alpha helpers, feed management, gateway helpers, x402 config, MPP helpers, and audit status helpers.
• Latest verified package coverage for cmd/search-gateway is in progress at 65.0%, with local gates passing for Go tests, secret scan, whitespace check, and ExecPlan XML validation.
• This is a source/test hardening entry, not a final 100% coverage claim and not a live deployment marker.

ATLAS-7 ticker canonicalization audit

The 215-row ATLAS-7 universe was audited against the SEC company tickers exchange reference and repaired where the current common-stock ticker was unambiguous.

• Fourteen high-confidence current ticker repairs were applied across DeltaSignal tables for the 215 universe.
• Fold Holdings, Inc. now surfaces as common-stock ticker FLD for CIK 0001889123; FLDDW is treated as a legacy warrant alias.
• Post-repair verification showed 0 SEC-current mismatches for the 215-row universe.
• Thirteen SEC-missing blank-ticker rows and one ambiguous common/warrant case remain intentionally unresolved rather than guessed.

Notification evidence digest and ATLAS-7 universe filtering

Notification summaries now expose the daily evidence workload behind an alert and filter latest-change notification selection to the ATLAS-7 universe.

• Emails include source route, feed compute time, changed-company count, CompanyFacts fact changes, changed/new files, raw delta bytes, candidate rows inspected, ATLAS-7 universe matches, universe source date, delivered tickers, delivered row count, and evidence-drilldown availability.
• Latest-change notification selection intersects daily-change candidates with the ATLAS-7 universe by ticker or CIK, so public digests do not promote non-universe candidates.
• Pre-deploy verification delivered a local email probe showing 109 changed companies, 5081 CompanyFacts fact changes, 7678466 raw delta bytes, 7 DeltaSignal candidates, and 1/215 ATLAS-7 universe match.
• The route remains an evidence-routing alert surface and does not provide personalized investment advice, recommendations, price targets, or order instructions.

Live ATLAS-history SPECTRA primary rollout

/v1/spectra-field-map/{ticker_or_cik} now prefers runtime SPECTRA generation from ATLAS-7 history over static contracts.

• Static SPECTRA contracts remain fallback only when runtime ATLAS history is unavailable or returns no rows.
• Production revision ca-web-intel-mcp--0000461 verified SPECTRA HTTP 200 for 215/215 ATLAS-7 rows, with 0 misses and 0 non-runtime responses.
• The full-universe probe used ticker addressing where available and zero-padded SEC CIK addressing for the 24 no-ticker ATLAS-7 rows.
• Full-probe SPECTRA responses used generation_mode=runtime_atlas_history, source_date=2026-06-04, points=42, static_contract=false, and real_data=true.
• Watchlist verification covered COIN, RIOT, MARA, WULF, CIFR, CRCL, and HOOD for alpha-signals, peer-ranking, and spectra-field-map.
• Weekly verification covered IREN and MSTR for atlas-history and spectra-field-map.
• The route remains evidence and diligence infrastructure only; it does not provide personalized investment advice, recommendations, or price targets.

Terminal broker envelope contract

GET /v1/contract/fields now publishes the terminal MCP-brokered ATLAS envelope contract.

• The terminal_broker contract version is deltasignal-terminal-broker-v1.
• The covered brokered datasets are covenant-stress, alpha-signals, and company-fundamentals.
• Terminal clients can treat summaries as opaque payloads keyed by endpoint_id; server-side ATLAS code owns route-specific structured parsing.
• The stable terminal envelope fields are endpoint_id, status, cache_status, quote_status, summary, evidence_summary, estimated_usd, cost_usd, and confirmation_token.
• Live verification passed on revision ca-web-intel-mcp--0000456; local regression coverage includes field-contract assertions for the broker datasets and envelope keys.
• No individual identity, wallet, credit amount, or usage data is included in this public changelog entry.

Parser field contract hardened

Production now returns the versioned parser-stable field set published by GET /v1/contract/fields.

• GET /v1/contract/fields remains the versioned source of truth with deltasignal-field-contract-v1.
• Company report composite responses now expose top-level summary.current_read, summary.issuer_state, summary.subscriber_takeaway, confidence, ticker, and source_date, while preserving data.ticker, data.workflow, data.status, and mcp_summary.
• Daily changes rows now retain parser-stable ticker fields, with fallback identifiers when a listed ticker is unavailable.
• The field contract explicitly documents daily row-level ticker paths and the stress compatibility fields stress_50pct / stressed_leverage_50pct.
• Live verification passed on revision ca-web-intel-mcp--0000455 with MSTR company report, latest daily changes, readiness, covenant stress, and field-contract probes.
• No individual identity, wallet, credit amount, or usage data is included in this public changelog entry.

MCP wallet-signed grant execution verified

Production MCP now honors wallet-signed grant context accepted by the outer x402/payment wrapper before API-key enforcement.

• Live verification passed on revision ca-web-intel-mcp--0000454 with an ephemeral enrolled wallet and a signed POST /mcp JSON-RPC tools/call to deltasignal_readiness.
• The live MCP response returned HTTP 200, X-DeltaSignal-Grant: wallet_signed_grant, a JSON-RPC result, and no JSON-RPC error.
• The temporary grant rows were removed after the smoke test, and the response did not echo the temporary private key or signature.
• Unauthenticated MCP discovery remains open: GET /mcp, initialize, and tools/list returned HTTP 200; the live tool list exposed 33 tools, including 29 deltasignal_* tools.
• Regression coverage includes TestHandleMCPAcceptsContextGrantFromX402Wrapper and focused MCP|SignedWalletGrant|FreeTierGrant tests.
• No individual identity, wallet, credit amount, or usage data is included in this public changelog entry.

Wallet-signed grant auth for zero-balance clients

Added a signed wallet-grant path before x402 payment middleware so enrolled EVM wallets can prove grant identity without requiring a funded x402 payment preflight.

• Callers send X-DeltaSignal-Wallet, X-DeltaSignal-Wallet-Timestamp, X-DeltaSignal-Wallet-Nonce, and X-DeltaSignal-Wallet-Signature.
• The signature uses EIP-191 personal_sign over the canonical DeltaSignal grant message and defaults to a 300-second freshness window.
• Matching requests consume the existing DB-backed grant counter and return billing_mode=wallet_signed_grant, payment_status=grant_applied, cost_usd=0, and actual_cost_usd=0.
• HTTP 402 responses, /help, and /openapi.json now expose wallet-grant auth metadata for agent and developer discovery.
• Live verification passed on revision ca-web-intel-mcp--0000453 with an ephemeral enrolled wallet; the temporary grant row was removed after the smoke test.
• No individual identity, wallet, credit amount, or usage data is included in this public changelog entry.

Verified wallet grant settlement bypass

Added source support for DB-backed verified-wallet grants: x402 verifies the signed payer wallet, matches it to the promo grant ledger, consumes the DB grant counter, returns a zero-amount grant settlement response, and skips paid settlement.

• No API key or separate grant identifier is required for enrolled wallet clients; payer identity comes from x402 verification, not from client-supplied wallet headers.
• The runtime records grant consumption in the existing DB counter and usage ledger, preserving route and tool metadata for audit.
• Billing metadata reports zero actual cost with billing_mode=verified_wallet_grant and payment_status=grant_applied for grant-covered calls.
• Raw wallet headers remain untrusted; callers without a matching verified wallet grant continue through normal x402 payment.
• Verification passed with GOWORK=off go test ./cmd/search-gateway; production rollout is separate from this source changelog entry.

Local regression smoke verified

Added an opt-in live-loop regression smoke for the live-loop route set and verified it locally against an internal-key gateway profile before production redeploy.

• The smoke runs without wallet-specific credentials by using an internal/test API key and the local gateway profile.
• Coverage includes pricing discovery, field contract, large-response guidance, no-ticker universe route locks, readiness, daily changes, alpha opportunities, top stressed, risk distribution, IREN/MSTR company reports, alpha signals, peer ranking, SPECTRA field maps, atlas history, alternate-day watchlist alpha/peer routes, and a known structured soft miss.
• Local verification passed with GOWORK=off go test ./cmd/search-gateway/..., focused acceptance tests, the local live-loop regression smoke script, and BASE_URL=http://127.0.0.1:3017 ./scripts/mcp-smoke.sh.
• This is source/local verification only. Live API rollout remains a separate backend redeploy step.

App renderer regression

Verify SwiftUI cards preserve source_date , computed_at_utc , payload_mode , compact flags, caveats, evidence references, x402 equivalent price, no-payment boundary, and non-advice language.

Expand public x402 probes

Readiness, company-report, and Morning Brief natural-language public unpaid probes now verify HTTP 402 body and x402 challenge headers. Extend the same check to any new paid public route.

REST / MCP / bundle drift comparison

Compare OpenAPI route inventory, MCP tools/list , and composite bundle outputs so route availability, tool names, prices, and payload modes stay synchronized.

Second-ticker company-report smoke

Repeat the company-report smoke with a second ticker from the latest daily-change slice to prove the aggregate is not only working for one issuer.

Public x402 launch and Wardenclyffe/OpenAPI contract rollout

Launched public DeltaSignal data routes as payable x402 seller endpoints while preserving internal API-key access.

• Launched public DeltaSignal data routes as payable x402 seller endpoints while preserving internal API-key access.
• Raised public paid routes from test defaults to the launch pricing schedule.
• Rolled out the Wardenclyffe/help/OpenAPI contract with updated readiness, help, schema shape, glossary, and debt coverage fields.
• Added MPP discovery alongside x402 for compatible public-agent marketplaces and registry crawlers.

Composite workflows, route discovery, and payment metadata

Published composite MCP presets for Morning Brief, Company Report, Pressure Board, Alpha Sweep, and Quick Ticker Check.

• Published composite MCP presets for Morning Brief, Company Report, Pressure Board, Alpha Sweep, and Quick Ticker Check.
• Added Arazzo workflow definitions so agents can inspect scenario plans before execution.
• Updated OpenAPI and route metadata for public clients that discover paid resources before execution.
• Improved x402 and MPP payment metadata so AgentCash-style crawlers can identify route prices and protocol families.

Natural Language briefs and compact evidence contracts

Natural Language briefs were formalized as evidence-to-Markdown compiler outputs, not new evidence sources.

• Natural Language briefs were formalized as evidence-to-Markdown compiler outputs, not new evidence sources.
• Renderer metadata includes mode, validation status, fallback reason, compiler/version fields, evidence hash where available, latency, tokens, cache status, and billing mode.
• Morning Brief Natural was updated to render returned alpha board evidence with issuer identity status, caveats, and non-advice language.
• Default monitoring outputs stay compact, with raw evidence exposed through explicit drilldown routes instead of hidden client-side fan-out.

Full-universe regression and issuer identity hardening

Added regression coverage for current REST surfaces, ATLAS-7 historical calculation surfaces, and MCP composite workflows.

• Added regression coverage for current REST surfaces, ATLAS-7 historical calculation surfaces, and MCP composite workflows.
• Extended company report and quick ticker check composite coverage across the issuer universe.
• Canonicalized Strategy Inc as MSTR across issuer routes, ATLAS history rows, supported-company search, and x402 examples.
• Canonicalized ambiguous Delta Signal issuer tickers and CIK aliases so public-company identity stays stable across CompanyFacts and ATLAS materialized rows.

Audit status, Morning Brief context, and public MCP discovery

Added the Azure-native ATLAS-7 audit status surface: GET /v1/atlas7/audit/latest and MCP deltasignal_atlas7_audit_status .

• Added the Azure-native ATLAS-7 audit status surface: GET /v1/atlas7/audit/latest and MCP deltasignal_atlas7_audit_status .
• Audit status reports freshness, last successful run, issuer count, operation count, failure counts, artifact prefix, and job metadata.
• Live audit verification reported 215 issuers, 1,935 operations, 0 failed operations, 0 historical failures, and 0 composite failures.
• Morning Brief was updated with alpha board audit context so first-time users can see board scope, issuer mix, low-quality demotions, and caveats.
• Public MCP discovery was opened before payment: initialize and tools/list stay inspectable, while tools/call remains protected by x402, API key, or an explicit free-tier grant.

Historical source dates, SPECTRA, and ATLAS-7 calculation history

Added historical source_date support for company fundamentals, covenant stress, peer ranking, alpha signals, and the MCP company-report flow.

• Added historical source_date support for company fundamentals, covenant stress, peer ranking, alpha signals, and the MCP company-report flow.
• Added first-class calculation-history surfaces: GET /v1/atlas7/calculation-history , GET /mpp/v1/atlas7/calculation-history , and MCP deltasignal_atlas7_calculation_history .
• Calculation-history rows preserve covenant, fundamentals, peer, alpha, SPECTRA input, source fields, payload hash, and evidence hash fields.
• MSTR SPECTRA was backfilled from real ATLAS history and exposed through GET /v1/spectra-field-map/MSTR .
• Company Report MCP was expanded to six legs by including SPECTRA as an advisory field-map support leg.

StrategiX Visual MCP and finished DeltaSignal deliverables

Published the public StrategiX Visual MCP discovery surface for evidence-to-visual artifact workflows.

• Published the public StrategiX Visual MCP discovery surface for evidence-to-visual artifact workflows.
• Added finished DeltaSignal Intelligence Deliverables pricing, including a single daily Morning Brief PDF, monthly daily-brief subscription, and heavy multi-issuer deep brief.
• Kept StrategiX execution internal-beta gated so public users are not asked to pay for tools that are not public-paid yet.

Company Report became a true OpenAPI-visible aggregate

Added live REST/x402 routes: GET /v1/company-report/{ticker} and POST /v1/bundles/company-report .

• Added live REST/x402 routes: GET /v1/company-report/{ticker} and POST /v1/bundles/company-report .
• The aggregate returns readiness, company fundamentals, alpha signals, peer ranking, covenant stress, and advisory SPECTRA field-map support in one bounded response.
• Public unauthenticated calls return the expected 402 x402 payment challenge.
• Internal live MSTR verification returned status=ok , partial=false , and 6 of 6 internal legs succeeded.
• Snapshot values from that verification: Strategy Inc, source date 2026-05-27 , alpha score 69 , peer rank 152/215 , stress live_stress_50pct=0.2566 , risk tier LOW , and SPECTRA mode atlas7_historical_spectra .

Public contract cleanup re-verified

Live OpenAPI is serving DeltaSignal ATLAS version 1.5.2 with 56 paths after the June 8 hardening rollout. Earlier audit snapshots showed 43 paths.

• Live OpenAPI is serving DeltaSignal ATLAS version 1.5.2 with 56 paths after the June 8 hardening rollout; this historical entry originally recorded an earlier 43-path snapshot.
• POST /mcp , GET /v1/readiness , GET /v1/company-report/{ticker} , and POST /v1/bundles/company-report are present in the public route contract.
• The alpha language contract now exposes research_posture and no longer exposes short_recommendation .
• Unpaid public GET /v1/readiness returns HTTP 402 with a JSON body containing error=payment_required , the route name, retry guidance, docs URL, and an x402 challenge pointer.
• Unpaid public GET /v1/company-report/MSTR?output_mode=compact returns HTTP 402 with the same developer-readable x402 pattern and a Base USDC challenge header.

Evidence replay semantics implementation track

Added deltasignal-evidence-replay-v1 to the free field-contract route in backend source.

• Added deltasignal-evidence-replay-v1 to the free field-contract route in backend source.
• The contract documents evidence_ref stability for the same route, normalized arguments, source date, limit, and offset.
• It documents evidence_hash as stable for identical canonical evidence preimages and changed when hashed payload, source date, page contents, or selected arguments change.
• It marks page.next_args , page.next_offset , page.next_tool , and daily-change evidence handles as replayable while the referenced source date remains available.
• Verification completed locally with focused field-contract and regression tests. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

Daily-change field-delta implementation track

Added deltasignal-daily-field-deltas-v1 to compact daily changes in backend source.

• Added deltasignal-daily-field-deltas-v1 to compact daily changes in backend source.
• The interim shape exposes CompanyFacts changed tags as field_deltas with field_name , source_date , ticker/CIK, threshold_crossed , and evidence_ref .
• prior_value , new_value , delta , and percent_delta are emitted as null unless the source row carries those values.
• The field-contract route documents this interim status so clients can consume it without mistaking tag-level deltas for numeric value changes.
• Verification completed locally with focused daily field-delta, field-contract, help, OpenAPI, pricing, billing, metadata, not-found, and coverage tests. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

Large-response handling implementation track

Added public help guidance for large DeltaSignal responses in backend source.

• Added public help guidance for large DeltaSignal responses in backend source.
• The help route now warns that company-report and daily-changes payloads can exceed 64 KB.
• The guidance calls out the AgentCash/Node path specifically: do not pipe large npx agentcash fetch stdout directly into another process.
• Recommended automation patterns are file redirects, compact or paginated routes, and clients that fully drain stdout before process exit.
• Verification completed locally with focused help and regression tests. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

Coverage discovery implementation track

Extended /companies in backend source with deltasignal-coverage-v1 .

• Extended /companies in backend source with deltasignal-coverage-v1 .
• Each issuer row now includes ticker , lookup_ticker , cik , entity_name , supported_routes , unavailable_routes , last_source_date , and coverage_status .
• The field-contract route documents the stable coverage discovery fields for automation.
• This lets clients preflight supported names and route availability before spending on paid drilldowns.
• Verification completed locally with focused companies, field-contract, help, OpenAPI, pricing, billing, metadata, and not-found tests. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

Response metadata envelope implementation track

Added deltasignal-response-metadata-v1 to the protected /v1/ response normalization path.

• Added deltasignal-response-metadata-v1 to the protected /v1/ response normalization path.
• Successful JSON object payloads now receive top-level metadata fields and a response_metadata object.
• The envelope includes request_id , route_uri , source_date , computed_at_utc , ticker , cost_usd , billing_mode , cache_hit , payload_mode , quality_flags , caveats , evidence_hash , evidence_hash_version , and latency_ms .
• Unavailable values are emitted as null or empty arrays where appropriate, so automation can parse a stable shape.
• Verification completed locally with focused billing, field-contract, help, OpenAPI, pricing, and not-found tests. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

Field contract discovery implementation track

Added free backend discovery route GET /v1/contract/fields .

• Added free backend discovery route GET /v1/contract/fields .
• The field contract returns deltasignal-field-contract-v1 , the canonical billing field cost_usd , not-found contract metadata, route aliases, and the path-ticker-free universe route set.
• The stable parser-path list includes the stable readiness, company-report, daily-changes, generic provenance, and stress aliases such as stress_50pct and stressed_leverage_50pct .
• The served OpenAPI and help response now publish /v1/contract/fields as a free support/discovery route in backend source.
• Verification completed locally with focused field-contract, help, OpenAPI, pricing, billing, and not-found tests. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

Universe route contract implementation track

Locked the five universe-scoped routes as path-ticker-free in backend help and served OpenAPI source.

• Locked the five universe-scoped routes as path-ticker-free in backend help and served OpenAPI source.
• The no-ticker route set is /v1/readiness , /v1/daily-changes/latest , /v1/alpha-opportunities , /v1/top-stressed , and /v1/risk-distribution .
• OpenAPI operations now carry x-deltasignal-route_scope=universe , x-deltasignal-path_ticker_free=true , and x-deltasignal-ticker_segment=forbidden .
• The help response includes an explicit policy: do not append /{ticker} , /UNIVERSE , or any other path segment to these routes.
• Verification completed locally with focused help/OpenAPI/pricing/billing/not-found tests. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

IREN SPECTRA coverage repair

Added deltasignal-web/public/spectra-field-map/IREN/contract.json so /v1/spectra-field-map/IREN can return a real field-map contract instead of a structured coverage miss.

• Added deltasignal-web/public/spectra-field-map/IREN/contract.json so /v1/spectra-field-map/IREN can return a real field-map contract instead of a structured coverage miss.
• The new IREN contract uses mode=atlas7_historical_spectra , version=SPECTRA-FIELD-MAP-v1 , company IREN Limited , CIK 0001878848 , and latest source date 2026-04-24 .
• The source lineage is preserved in artifacts/spectra-field-map/IREN/atlas_history_source.json with three real ATLAS-7 atlas-history rows.
• Added a regression test that serves the IREN public contract and asserts real_data=true with three returned SPECTRA points.

Structured not-found implementation track

Added a shared structured not_found response contract in backend source.

• Added a shared structured not_found response contract in backend source.
• Route/ticker misses now expose status=not_found , reason , coverage_state , retry_after_days , route_uri , ticker or request key, request ID, and not_found_contract_version .
• SPECTRA misses still have an explicit semantics path: reason=historical_field_map_contract_missing , coverage_state=not_available_for_issuer , and a seven-day retry hint.
• The shape is also wired into fundamentals, alpha signals, covenant stress, peer ranking, daily changes, daily-change evidence, and field-map misses.
• Verification completed locally with focused not-found, billing, pricing, help, and OpenAPI tests. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

Canonical billed-response fields implementation track

Added a shared backend billing normalizer for protected priced /v1/ routes.

• Added a shared backend billing normalizer for protected priced /v1/ routes.
• Successful JSON object responses now receive canonical numeric cost_usd plus quoted_cost_usd , actual_cost_usd , billing_mode , billing_contract_version , route identity, payment status, and request ID.
• x402 paid responses preserve route price as both quote and actual cost. Internal API-key and free-tier grants report actual_cost_usd=0 while preserving the route quote for budgeting.
• Errors, arrays, non-JSON bodies, and unpriced free discovery routes such as /v1/pricing are not rewritten by the billing normalizer.
• Verification completed locally with focused billing/pricing/help/OpenAPI tests. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

Pricing discovery implementation track

Added the first live-loop contract slice in backend source: GET /v1/pricing .

• Added the first live-loop contract slice in backend source: GET /v1/pricing .
• The route is designed as free discovery and returns a machine-readable x402 route catalog with route_uri , HTTP method, price_usd , billing mode, ticker requirements, and pricing source.
• The pricing contract declares cost_usd as the canonical billed-response ledger field and treats quoted_cost_usd / actual_cost_usd as supplemental aliases when route-specific flows emit them.
• The served OpenAPI document now publishes /v1/pricing as a free discovery route in the backend source.
• Verification completed locally with targeted pricing/help/OpenAPI tests and the full go test ./cmd/search-gateway/... package suite. Live backend deployment verified on revision ca-web-intel-mcp--0000450.

Monitoring and contract maturity

Move from pull-only reports toward durable monitoring and explicit field stability.

• Add webhook/subscription routes for material changes with event IDs, delivery signatures, replay cursors, field deltas, provenance, and evidence refs.
• Add GET /v1/contract/changelog and GET /v1/contract/fields for stable field paths, deprecation windows, migration notes, and versioned daily-change fields.
• Document route classes: free discovery, cheap freshness, paid compact, paid evidence, and internal/backend-relayed access.
• Constrain renderer posture values to non-advice labels such as constructive_evidence_screen , watchlist_candidate , risk_elevated , provenance_limited , data_stale , and insufficient_evidence .

Scale and freshness ergonomics

Add preflight and batch surfaces so clients do not need repeated paid single-name calls just to discover coverage, freshness, or availability.

• Add GET /v1/companies , GET /v1/companies?changed_since=... , and GET /v1/ticker-freshness/{ticker} .
• Extend company-report bundle support to tickers: [] with per-ticker result, partial flag, provenance, and error state.
• Add snapshot metadata for company reports: snapshot_id , start/end timestamps, section count, max section skew, and whether sections share the same data-as-of boundary.

Universal evidence contract

Add one mandatory provenance object across readiness, company report, daily changes, evidence drilldowns, alpha signals, fundamentals, peer ranking, covenant stress, and SPECTRA. Missing fields should return null , not disappear.

• Fields: captured_at , observed_at , published_at , data_as_of , computed_at_utc , source_date , accession_number , evidence_ref , evidence_hash , schema_version , contract_version .
• Add semantic daily-change deltas with field_path , prior_value , new_value , delta_type , threshold_crossed , materiality_score , and evidence identifiers.
• Document whether evidence refs are stable, what evidence hashes cover, how pagination affects hashes, and whether refs can be replayed after refresh.

P1 standard provenance source implementation

Added deltasignal-provenance-v1 to the protected /v1/ response normalization path in backend source.

• Added deltasignal-provenance-v1 to the protected /v1/ response normalization path in backend source.
• Successful JSON object responses now receive a top-level provenance object with route identity, source_date , computed_at_utc , ticker, filing/accession fields where available, evidence hash/ref fields, data source, quality flag, and derived/proprietary markers.
• If a route already emits provenance , the envelope preserves existing route-specific keys and fills only missing standard keys.
• GET /v1/contract/fields now documents the standard provenance field set, merge policy, and derived-evidence policy.
• Verification completed locally with GOWORK=off go test ./cmd/search-gateway/... , HTML/XML/module validation for the source spec and ExecPlan, and clean deployment-worktree commit 730def3 . Backend rollout is separate from this changelog publication.

P0 contract-hardening source implementation

Added deltasignal-route-scope-v1 in backend source so no-ticker universe routes called with extra path segments return structured HTTP 400 invalid_path_scope instead of ambiguous 404 behavior.

• Added deltasignal-route-scope-v1 in backend source so no-ticker universe routes called with extra path segments return structured HTTP 400 invalid_path_scope instead of ambiguous 404 behavior.
• The protected no-ticker set is /v1/readiness , /v1/daily-changes/latest , /v1/alpha-opportunities , /v1/top-stressed , and /v1/risk-distribution .
• /v1/pricing route entries now include lifecycle and scope metadata: path_template , status , deprecated , replaced_by , billable , and route_scope .
• Successful protected /v1/ JSON object responses now include billing_status at the top level and inside response_metadata .
• Structured not_found payloads now include reason_code , billing_behavior=not_charged , and cost_usd=0 .
• Verification completed locally with GOWORK=off go test ./cmd/search-gateway/... , HTML/XML/module validation for the source spec and ExecPlan, and clean deployment-worktree commit 7a80e86 . Backend rollout is separate from this changelog publication.

Second-ticker company-report smoke

Repeat the company-report smoke with a second ticker from the latest daily-change slice to prove the aggregate is not only working for one issuer.

REST / MCP / bundle drift comparison

Compare OpenAPI route inventory, MCP tools/list, and composite bundle outputs so route availability, tool names, prices, and payload modes stay synchronized.

Expand public x402 probes

Readiness, company-report, and Morning Brief natural-language public unpaid probes now verify HTTP 402 body and x402 challenge headers. Extend the same check to any new paid public route.

App renderer regression

Verify SwiftUI cards preserve source_date, computed_at_utc, payload_mode, compact flags, caveats, evidence references, x402 equivalent price, no-payment boundary, and non-advice language.