Reported issues for AINumbers Fintech Intelligence Suite
Pod holds 9 of 9 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to AINumbers Fintech Intelligence Suite.
Most discussed
Vendor drift: worker data/ behind site main
Scheduled vendor-freshness check (OF-4) found the worker's vendored data/chaingraph.json and/or kernels/ diverged from PostOakLabs/ainumbersmain beyond one schedule cycle (6h).
This means a site merge touched graph shards/chaingraph.json with no follow-on vendor land — the worker is serving a stale catalog.
Fix: in mcp-apps-poc/, run node generate.mjs, commit data/ + kernels/, push (see CONTRACT §A4).
Failing run: https://github.com/PostOakLabs/ainumbers-mcp-apps/actions/run
Read the thread · 2026-08-29 · open · external user · 10 comments
Vendor drift: worker data/ behind site main
Scheduled vendor-freshness check (OF-4) found the worker's vendored data/chaingraph.json and/or kernels/ diverged from PostOakLabs/ainumbersmain beyond one schedule cycle (6h).
This means a site merge touched graph shards/chaingraph.json with no follow-on vendor land — the worker is serving a stale catalog.
Fix: in mcp-apps-poc/, run node generate.mjs, commit data/ + kernels/, push (see CONTRACT §A4).
Failing run: https://github.com/PostOakLabs/ainumbers-mcp-apps/actions/run
Read the thread · 2026-08-23 · closed · external user · 1 comment
Vendor drift: worker data/ behind site main
Scheduled vendor-freshness check (OF-4) found the worker's vendored data/chaingraph.json and/or kernels/ diverged from PostOakLabs/ainumbersmain beyond one schedule cycle (6h).
This means a site merge touched graph shards/chaingraph.json with no follow-on vendor land — the worker is serving a stale catalog.
Fix: in mcp-apps-poc/, run node generate.mjs, commit data/ + kernels/, push (see CONTRACT §A4).
Failing run: https://github.com/PostOakLabs/ainumbers-mcp-apps/actions/run
Read the thread · 2026-08-21 · closed · external user · 4 comments
Vendor drift: worker data/ behind site main
Scheduled vendor-freshness check (OF-4) found the worker's vendored data/chaingraph.json and/or kernels/ diverged from PostOakLabs/ainumbersmain beyond one schedule cycle (6h).
This means a site merge touched graph shards/chaingraph.json with no follow-on vendor land — the worker is serving a stale catalog.
Fix: in mcp-apps-poc/, run node generate.mjs, commit data/ + kernels/, push (see CONTRACT §A4).
Failing run: https://github.com/PostOakLabs/ainumbers-mcp-apps/actions/run
Read the thread · 2026-08-20 · closed · external user · 4 comments
Vendor drift: worker data/ behind site main
Scheduled vendor-freshness check (OF-4) found the worker's vendored data/chaingraph.json and/or kernels/ diverged from PostOakLabs/ainumbersmain beyond one schedule cycle (6h).
This means a site merge touched graph shards/chaingraph.json with no follow-on vendor land — the worker is serving a stale catalog.
Fix: in mcp-apps-poc/, run node generate.mjs, commit data/ + kernels/, push (see CONTRACT §A4).
Failing run: https://github.com/PostOakLabs/ainumbers-mcp-apps/actions/run
Read the thread · 2026-08-18 · closed · external user · 1 comment
Vendor drift: worker data/ behind site main
Scheduled vendor-freshness check (OF-4) found the worker's vendored data/chaingraph.json and/or kernels/ diverged from PostOakLabs/ainumbersmain beyond one schedule cycle (6h).
This means a site merge touched graph shards/chaingraph.json with no follow-on vendor land — the worker is serving a stale catalog.
Fix: in mcp-apps-poc/, run node generate.mjs, commit data/ + kernels/, push (see CONTRACT §A4).
Failing run: https://github.com/PostOakLabs/ainumbers-mcp-apps/actions/run
Read the thread · 2026-08-18 · closed · external user · 2 comments
Vendor drift: worker data/ behind site main
Scheduled vendor-freshness check (OF-4) found the worker's vendored data/chaingraph.json and/or kernels/ diverged from PostOakLabs/ainumbersmain beyond one schedule cycle (6h).
This means a site merge touched graph shards/chaingraph.json with no follow-on vendor land — the worker is serving a stale catalog.
Fix: in mcp-apps-poc/, run node generate.mjs, commit data/ + kernels/, push (see CONTRACT §A4).
Failing run: https://github.com/PostOakLabs/ainumbers-mcp-apps/actions/run
Read the thread · 2026-08-12 · closed · external user · 2 comments
Vendor drift: worker data/ behind site main
Scheduled vendor-freshness check (OF-4) found the worker's vendored data/chaingraph.json and/or kernels/ diverged from PostOakLabs/ainumbersmain beyond one schedule cycle (6h).
This means a site merge touched graph shards/chaingraph.json with no follow-on vendor land — the worker is serving a stale catalog.
Fix: in mcp-apps-poc/, run node generate.mjs, commit data/ + kernels/, push (see CONTRACT §A4).
Failing run: https://github.com/PostOakLabs/ainumbers-mcp-apps/actions/run
Read the thread · 2026-08-11 · closed · external user · 1 comment
Most recent
Vendor drift: worker data/ behind site main
Scheduled vendor-freshness check (OF-4) found the worker's vendored data/chaingraph.json and/or kernels/ diverged from PostOakLabs/ainumbersmain beyond one schedule cycle (6h).
This means a site merge touched graph shards/chaingraph.json with no follow-on vendor land — the worker is serving a stale catalog.
Fix: in mcp-apps-poc/, run node generate.mjs, commit data/ + kernels/, push (see CONTRACT §A4).
Failing run: https://github.com/PostOakLabs/ainumbers-mcp-apps/actions/run
Read the thread · 2026-08-23 · closed · external user · 1 comment
The remaining reports are on the project's issue tracker.