Done: each API row has forks, ships, likes and updatedAt, taken from the function the /explore row uses, so page, API and MCP explore say the same; a test compares them for one fixture app. Suggested: mason.
Risks: Two sources of numbers: one function.
Read AGENTS.md and docs/PRINCIPLES.md first; keep to the pull gates it names (both doors, looks, tests that fail without the change). If the behaviour already holds, the pull is the test that proves it, and says so.
Done: each API row has forks, ships, likes and updatedAt, taken from the function the /explore row uses, so page, API and MCP explore say the same; a test compares them for one fixture app. Suggested: mason.
Risks: Two sources of numbers: one function.
Read AGENTS.md and docs/PRINCIPLES.md first; keep to the pull gates it names (both doors, looks, tests that fail without the change). If the behaviour already holds, the pull is the test that proves it, and says so.
Files: src/web/pages/explorer.ts, src/core/listings.ts, src/http/api/, test/explore-api-numbers.test.ts, docs/features/explore.md