Skip to content

spec(FIX-898): Recover critical financial evidence from IPO filings - #785

Closed
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/fix-898-spec-generation-automation-a961
Closed

cursor[bot] wants to merge 1 commit into
mainfrom
cursor/fix-898-spec-generation-automation-a961

Conversation

@cursor

@cursor cursor Bot commented Jul 17, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Implementation spec for FIX-898.

Adds a bounded critical-source recovery path for the trading desk when EDGAR Company Facts and Yahoo miss valuation-critical financials (the SPCX / newly listed IPO failure mode). Deterministic SEC registration/prospectus candidates (S-1, 424B*) first, then one capped LLM extract, hard validation before promoting into financialsData, honest unavailable + recoveryAudit otherwise.

Docs-only PR — no changeset (BP-022). This PR is for spec review only; fsd:implement-issue closes it unmerged when implementation starts.

Necessity verdict

Build as scoped — correctness gap in the lab app's statement spine; existing investigate cannot promote typed numbers into financialsData.

Key decisions (top 5)

  1. Recovery in the statement-tool live chain (single-flight), not investigate. Investigate stays citation-only.
  2. REGISTRATION_FORMS separate from PERIODIC_FORMS. MD&A/8-K extractors unchanged.
  3. Hard validation before any spine write. No narrative promotion; no zero-fill; normalize to USD billions.
  4. Not cost-gated by costPreset. Correctness path may spend one model call on fast after deterministic miss.
  5. Sparse companyfacts is an explicit new miss branch (today edgar+nulls short-circuits). Plus recoveryAudit + edgar-prospectus source tag; FIX-808 case prepared but not blocked.

Validator fixes folded in

  • Real schema field names (operating, cashAndEquivalents)
  • BP-011: non-block LLM extract leaf (not generator-from-handler)
  • Record vs fixture mode clarified
  • No clobber of Yahoo siblings; toSpine: false gated
  • USD billions promote required

Linear sync gap

Cloud automation has no Linear API (LINEAR_API_KEY not injected; no Linear MCP). Could not: move issue to In Spec Dev / In Spec Review, attach Linear document, comment, or reframe the issue description. Repo spec + this PR are the reviewable artifacts; Linear mirror needs a follow-up with credentials.

Spec document

docs/specs/FIX-898.md

Open questions (defaults chosen)

  1. Sibling registrationFilings (default) vs mixing into recentFilings
  2. SEC-linked IR URLs only (default)
  3. Synthetic SPCX HTML fixture as primary regression (default)
Open in Web View Automation 

Greptile Summary

This PR specifies recovery of valuation-critical financials from IPO filings. The main changes are:

  • Adds SEC registration and prospectus discovery after structured-provider misses.
  • Defines deterministic and bounded model extraction with hard validation.
  • Adds single-flight spine promotion and a structured recovery audit.
  • Plans fixtures, tests, documentation, and a goal check for the recovery path.

Confidence Score: 4/5

The implementation contract needs fixes for filing coverage and issuer-IR provenance before it is used to build the recovery path.

Some valid 424B prospectuses can be filtered out before recovery. Accepted issuer-IR evidence has no matching statement source value. The hard FCF gate lacks a deterministic tolerance.

docs/specs/FIX-898.md

T-Rex T-Rex Logs

What T-Rex did

  • T-Rex ran a focused executable probe against a representative 424B2 filing and observed that the periodic-filings path returned no recent filings, and the provider exports neither REGISTRATION_FORMS nor fetchRegistrationCandidates.
  • T-Rex confirmed via a runtime check that the registration-candidate provider and critical-financials-recovery module do not exist at head, so no implemented path can produce the no-candidates outcome.
  • T-Rex reproduced issuer-IR cannot be stored: real income statement, cashflow, and balance-sheet schemas rejected source: issuer-ir with invalid_enum_value, and the edgar-prospectus fallback tag was also rejected; the Vitest run exited with code 0.
  • T-Rex ran the requested verification but local artifact references were not uploaded.

View all artifacts

T-Rex Ran code and verified through T-Rex

Important Files Changed

Filename Overview
docs/specs/FIX-898.md Defines the IPO financial-recovery implementation, with gaps in form coverage, provenance shape, and reconciliation rules.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Load statement] --> B{Company Facts usable?}
  B -->|Yes| S[Write subject spine]
  B -->|No or sparse| C{Yahoo usable?}
  C -->|Yes| S
  C -->|No| D[Single-flight recovery]
  D --> E[Discover registration filings]
  E --> F[Fetch up to three documents]
  F --> G[Deterministic extraction]
  G --> H{Candidate sufficient?}
  H -->|No| I[One bounded model extraction]
  H -->|Yes| J[Hard validation]
  I --> J
  J -->|Pass| K[Normalize and promote]
  J -->|Fail| L[Keep unavailable]
  K --> M[Write promoted audit]
  L --> N[Write failure audit]
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
  A[Load statement] --> B{Company Facts usable?}
  B -->|Yes| S[Write subject spine]
  B -->|No or sparse| C{Yahoo usable?}
  C -->|Yes| S
  C -->|No| D[Single-flight recovery]
  D --> E[Discover registration filings]
  E --> F[Fetch up to three documents]
  F --> G[Deterministic extraction]
  G --> H{Candidate sufficient?}
  H -->|No| I[One bounded model extraction]
  H -->|Yes| J[Hard validation]
  I --> J
  J -->|Pass| K[Normalize and promote]
  J -->|Fail| L[Keep unavailable]
  K --> M[Write promoted audit]
  L --> N[Write failure audit]
Loading

Fix All in Cursor

Reviews (1): Last reviewed commit: "spec(FIX-898): critical financial recove..." | Re-trigger Greptile

Greptile also left 3 inline comments on this PR.

Implementation spec for bounded prospectus/registration-form recovery when
EDGAR companyfacts and Yahoo miss valuation-critical fields (SPCX-shaped
failure). Docs-only; no changeset (BP-022).

Co-authored-by: Jake Hoffner <jhoffner@users.noreply.github.com>
@linear-code

linear-code Bot commented Jul 17, 2026

Copy link
Copy Markdown

FIX-898

@vercel

vercel Bot commented Jul 17, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
flow-state-dev-kitchen-sink Ready Ready Preview, Comment Jul 17, 2026 8:04pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
flow-state-dev-docs Ignored Ignored Preview Jul 17, 2026 8:04pm
flow-state-dev-ui Ignored Ignored Preview Jul 17, 2026 8:04pm

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/simplify review — spec-only PR

Verdict: COMMENT (approve-quality architecture; tighten the spec before implementation). The core problem diagnosis and the rejected alternatives (investigate promote, widening PERIODIC_FORMS, soft LLM-only confidence) are right. What risks over-building is less the ladder itself than how the spec tells implementers to wire it: three parallel statement handlers + a combined critical-miss trigger + record/replay + a rich recoveryAudit + optional disclosure surfacing + a new goal family — without a FIX-895-style v1 reconciliation that subtracts modules and names one coordinator.

What is the right approach (keep)

  • Statement-tool live chain (not Phase 1 investigate): matches writeSubjectSpine / financialsData and BP-011.
  • Sparse companyfacts → miss before Yahoo/recovery: today mapEdgarCompanyFacts returns source: "edgar" with null criticals and short-circuits the chain — without this, IPO recovery is a no-op.
  • REGISTRATION_FORMS separate from PERIODIC_FORMS: aligns with edgar-filings.ts / latestPeriodic and disclosure prompts.
  • Deterministic SEC HTML first, one bounded LLM, hard validation, no partial promote: same discipline as PDF holdings (extract-holdings-generator + reconcile), without calling a generator from handlers.
  • Run-local single-flight for recovery (not 120s getOrFetch for LLM outcomes): correct.

Where the spec goes too far (simplify before impl)

  1. “Wire into three statement tools” understates the coordinator. Combined critical miss is defined across income + cashflow after companyfacts + Yahoo. With fundamentals fan-out in .parallel, per-tool recovery can fire early (sibling Yahoo still in flight), duplicate SEC/LLM work even with single-flight, or write recoveryAudit while the spine is partial. The spec already says the recovery runtime is the sole recoveryAudit writer — make that explicit as the only entry point: shared loadStatementLive(field) that (a) runs EDGAR→Yahoo, (b) awaits the same (ticker,date) inflight recovery Promise, (c) never implements “combined miss” independently in three files. BP-024 factory can stay deferred, but one shared loader module should be required in v1, not “deepening.”

  2. Module fan-out for v1. prospectus-financials.ts + validate-financial-candidate.ts + critical-financials-recovery.ts + recover-financials-extract.ts + prompt is a lot for a lab feature. Consider collapsing validation + USD-billions promote into the recovery runtime until a second consumer exists; keep deterministic HTML extract separate only if unit-tested in isolation.

  3. recoveryAudit surface vs consumers. FIX-781 consumption is explicitly non-blocking. Until a reader lands, a smaller v1 (attempted, outcome, urls, rejectionReasons) may suffice; outcome: "skipped" vs absent audit is redundant. Trim recoveredSource: "issuer-ir" if v1 is SEC-only (§11 #2).

  4. Disclosure deliverable is optional for AC. Recovery can call fetchRegistrationCandidates directly. Extending get_sec_filings / EdgarFilingsPayload is polish — mark non-blocking in §1 deliverables so spine work does not drag disclosure + prompt edits.

  5. Pre-existing perf: 3× fetchCompanyFacts. Parallel statement tools (and quant composites) already hit companyfacts independently. FIX-898 should require single-flight or getOrFetch on fetchCompanyFacts as part of the same change (or a named prerequisite step) — orthogonal win, large constant-factor cut on every US name.

  6. Record/replay ordering. Per-tool recordIfRecording after each load() can persist pre-recovery unavailable while spine later shows edgar-prospectus. Spec should state: record after recovery settles for statement tools, or record the post-recovery payload only.

  7. Goal check scope. goals/trading-desk-financials/… should prefer spine/unit tests or a thin probe (pattern: goals/trading-desk-portfolio/*/run.mts), not full analyze + runSummary unless explicitly optional live EDGAR. fsd:verify-trading-desk is the wrong default AC ladder for statement fields.

  8. Spec shape vs FIX-895. A short §0 v1 reconciliation (authoritative: shared loader + coordinator, defer disclosure goal polish, minimal audit, no cheerio/jsdom — reuse edgar-filings edgarFetch / strip patterns) would prevent implementers from treating every §4.1 row as mandatory day one.

Third-party / reuse (no new deps needed)

  • No cheerio/jsdom in the desk today; edgar-filings.ts extractSection strip pattern is the precedent for prospectus text.
  • Export/refactor shared submissions iteration from edgar-filings.ts instead of a parallel fetchSubmissions in edgar-registration.ts.
  • Reuse billions normalization from edgar-companyfacts.ts / yahoo-timeseries.ts when promoting FinancialCandidate.

Intentional complexity (not asking to revert)

  • LLM on fast for critical miss: product choice vs investigate gating; spec should keep the rationale (already in decision #4) but note the cost/latency tradeoff on fundamentals critical path.

Performance

  • Bounded ≤3 HTML fetches is fine; risk is multi-MB bodies + sync parse on the event loop and duplicate submissions with disclosure analyst unless submissions are cached (getOrFetch for read-only SEC JSON is appropriate).

Skipped (larger than spec PR / product call)

  • Deterministic-only on fast, LLM on full only.
  • Orchestration-level .tap after fundamentals tools instead of in-tool recovery (cleaner hot path, more invasive).

Happy to approve after a light spec pass: mandatory shared loader/coordinator, §0 v1 scope, record ordering, companyfacts dedupe, and demote disclosure/goal/docs templates to non-blocking where AC is spine-only.

Open in Web View Automation 

Sent by Cursor Automation: Review For Best Approach

Comment thread docs/specs/FIX-898.md
- **Recovery:** Add single-flight critical recovery + pure validation leaf;
treat sparse companyfacts (`source: "edgar"` with null critical fields) as
a miss (today only throws fall through); wire into the three statement
tools; add `edgar-prospectus` source tag + `recoveryAudit` on

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simplify wiring: "wire into the three statement tools" fights the combined critical-miss definition (§4.2). Recommend making a shared loadStatementLive + single recovery coordinator a v1 requirement (sole recoveryAudit writer), with the three handlers only passing field/tool — same as you already do for EDGAR→Yahoo duplication today. Defer BP-024 factory, not the shared loader.

Comment thread docs/specs/FIX-898.md
| Deterministic extract | Create `labs/trading-desk/lib/providers/prospectus-financials.ts` — HTML → typed candidate (pure where possible) |
| Validation | Create `labs/trading-desk/flows/analysis/lib/validate-financial-candidate.ts` (pure) |
| Single-flight recovery | Create `labs/trading-desk/flows/analysis/tools/runtime/critical-financials-recovery.ts` |
| LLM extract (bounded) | Create a **non-block** leaf under `tools/runtime/` (e.g. `recover-financials-extract.ts` + prompt) — same *discipline* as `flows/portfolio/extract-holdings-generator.ts` (transcribe + validate), but **not** a `generator` block invoked from a handler (BP-011). Prefer direct model+schema call from the recovery runtime, or a `router` if block kinds must differ (`get_social_sentiment.ts` precedent). |

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

v1 module budget: Four new runtime/flow files + prompt is heavy. Consider spec-authoritative merge of validation + promote mapping into critical-financials-recovery.ts for v1; keep prospectus-financials.ts only if deterministic extract has its own test matrix. Avoid a third normalization dialect — point implementers at edgar-companyfacts.ts / yahoo-timeseries.ts billions helpers.

Comment thread docs/specs/FIX-898.md
after companyfacts + Yahoo attempts, the **combined** critical set across
income + cashflow still lacks valuation-critical fields. Use **real schema
field names**:

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Race / wasted work: "combined critical miss" while income/cashflow/balance load in parallel needs an explicit rule: recovery must not evaluate until all three Yahoo legs have settled (or coordinator reads spine after shared inflight Promise). Otherwise single-flight dedupes duplicate LLM but not premature SEC work.

Comment thread docs/specs/FIX-898.md
* Never leave prospectus dollars on the spine.
*/

export type RecoveryAudit = {

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Audit minimalism: Until FIX-781 consumes this, consider shrinking v1 recoveryAudit (drop redundant skipped vs absent; defer issuer-ir in recoveredSource). Session citationIntegrity is the right analogy, wrong shape — keep audit on financialsData only.

Comment thread docs/specs/FIX-898.md
with scale.

5. **Single-flight recovery runtime + source tag + recoveryAudit**
- Wire into three statement tools; gate on subject/`toSpine`.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Step 5 should name shared loader extraction as part of this step (not §8 deepening). Parallel spine test is good — add assertion that record mode captures post-recovery payloads, not pre-recovery unavailable per tool.

Comment thread docs/specs/FIX-898.md
attempts).

**Goal check:** Add
`goals/trading-desk-financials/ipo-prospectus-recovery/` (name flexible) that

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Goal path: prefer vitest/spine probe or tsx goal over full analyze + runSummary for CI-adjacent checks (see goals/trading-desk-portfolio/*/run.mts). Optional live EDGAR ticker is fine; don't make fsd:verify-trading-desk the default AC.

Comment thread docs/specs/FIX-898.md

**Deepening opportunities (follow-up via `fsd:improve-codebase-architecture`):**

- Factory for the three near-identical statement handlers (BP-024).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Promote companyfacts single-flight / getOrFetch in fetchCompanyFacts from follow-up to FIX-898 step 0 or 2 — fixes 3× HTTP today and amplifies every IPO-miss path. Statement-tool factory can stay here.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9d3b82f571

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/specs/FIX-898.md
|-------|--------|
| CIK matches `resolveCik(ticker)` | reject wrong-company |
| Conformed name fuzzy-match vs profile/submissions name (non-empty) | reject |
| `periodEnd` present and ≤ run `date` + small grace; not decades stale vs listing | reject stale |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Reject filings published after the run date

For historical analyses, candidate discovery reads the current SEC submissions catalog, but this validation only bounds periodEnd; a 424B4 filed after the requested date can contain an older audited period and therefore pass, leaking future information into the financials spine. Require filingDate <= run date during discovery or validation and add a historical-run regression.

Useful? React with 👍 / 👎.

Comment thread docs/specs/FIX-898.md
Comment on lines +205 to +207
**Single-flight:** Parallel tools share one **run-local** in-flight Promise per
`(ticker, date)` (do **not** use process-TTL `getOrFetch` for LLM recovery —
failed attempts must not stick across sessions for 120s). Recovery may fill

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Use request-scoped runOnce for the recovery

A Promise map keyed only by (ticker, date) is not run-local: concurrent sessions for the same ticker/date can share an attempt, while deleting the entry on settlement lets a slower sibling tool launch a second paid extraction. BlockContext.runOnce already memoizes per (requestId, userKey), including concurrent calls and retries (packages/core/src/types/block.ts), so the spec should require that request-scoped primitive instead of a module map.

Useful? React with 👍 / 👎.

Comment thread docs/specs/FIX-898.md
Comment on lines +313 to +315
handlers — do **not** `block.run` a `generator` from inside them. Use a
plain async model+schema helper owned by the recovery runtime, or a `router`
if a true generator block is required (`get_social_sentiment.ts`). The

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Route extraction through the generator runtime

The preferred plain model helper bypasses the generator runtime behavior implemented in packages/core/src/blocks/generator.ts, including model resolution, ctx.signal cancellation, usage/cost reporting, and generator test instrumentation. On a recovery miss this can leave a paid call running after cancellation and undercount the run summary, so specify a router/sequencer-owned generator path like get_social_sentiment.ts rather than a direct SDK call from the handler.

Useful? React with 👍 / 👎.

Comment thread docs/specs/FIX-898.md
Comment on lines +323 to +327
- **Modes:**
- `fixture` — load fixtures only; never call live recovery (replay recorded
`edgar-prospectus` / `unavailable` + audit).
- `live` / `record` — run the live chain **including** recovery, then
`recordIfRecording` on `record` (same as today's statement tools).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Persist and hydrate the recovery audit in fixture mode

The current recordIfRecording/loadFixture path records and returns only each statement tool's output, while recoveryAudit is a separate financialsData field; because fixture mode also skips the recovery runtime (its sole writer), recorded audits cannot be replayed and the fixture goal requiring outcome === "promoted" will fail. Define a dedicated recorded audit artifact and fixture hydration path, or include the audit in a schema that the recorder actually persists.

Useful? React with 👍 / 👎.

Comment thread docs/specs/FIX-898.md
Comment on lines +224 to +226
export const REGISTRATION_FORMS = new Set([
"S-1", "S-1/A", "424B4", "424B3", "F-1", "F-1/A",
]);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Wildcard Promise Excludes Valid Forms

The design promises 424B* recovery, but this allowlist accepts only 424B3 and 424B4. When EDGAR reports an available prospectus as another 424B variant, candidate discovery drops it and records no-candidates, leaving the financials unavailable despite an eligible SEC filing.

Fix in Cursor

Comment thread docs/specs/FIX-898.md
Comment on lines +287 to +290
};
```

Extend `sourceTag` with `"edgar-prospectus"`. Extend

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Issuer-IR Source Cannot Be Stored

Validation permits promotion from a SEC-linked issuer-IR URL and the audit can report issuer-ir, but the statement source enum gains only edgar-prospectus. A valid issuer-IR recovery must therefore either fail statement-schema validation or be stored with false EDGAR provenance.

Artifacts

Repro: focused executable test exercising the real financial statement schemas with issuer-IR provenance

  • Contains supporting evidence from the run (text/typescript; charset=utf-8).

Repro: Vitest configuration used to execute the focused schema harness

  • Contains supporting evidence from the run (text/typescript; charset=utf-8).

Repro: verbose runtime output showing issuer-ir and edgar-prospectus sourceTag validation failures

  • Keeps the command output available without making the summary code-heavy.

View artifacts

T-Rex Ran code and verified through T-Rex

Fix in Cursor

Comment thread docs/specs/FIX-898.md
Comment on lines +301 to +303
| `scale` parsed from table header / explicit units — never inferred from magnitude | reject if ambiguous |
| At least revenue + operatingIncome + (FCF or operating+capex) present after scale | reject insufficient |
| If operating + capex + FCF all present: `|FCF − (operating − \|capex\|)|` within tolerance | reject unreconciled |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Reconciliation Boundary Is Undefined

The required FCF gate says only “within tolerance” without defining an absolute or relative threshold. Rounded prospectus tables can therefore be rejected by one implementation and accepted by another, making promotion of the same filing nondeterministic and potentially leaving valuation-critical fields unavailable.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Cursor

@jhoffner jhoffner closed this Jul 23, 2026
@jhoffner
jhoffner deleted the cursor/fix-898-spec-generation-automation-a961 branch July 23, 2026 15:17

This branch was successfully deployed

1 active deployment
Preview – flow-state-dev-kitchen-sink — 9d3b82f5 Deployed Jul 17, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants