shinnslist

changelog LIVE

What every sprint actually shipped, sprint by sprint. This page is generated from the real git history of the shinnslist repo (git log) on 2026-09-29 — every entry is a real commit, rendered word-for-word, and every entry cites the commit it came from. Nothing here is invented.

the whole contract, in one paragraph. This page covers the 326 commits in the repo at generation time, head b98f01a. Every entry below carries its commit hash; verify any entry yourself with git log --oneline | grep <hash> or git show <hash>. If a commit is unclear, it is described plainly in the commit's own words — the commit is the description. The only numbers printed on this page that are not part of a commit message are the 326-commit total itself (check it with git rev-list --count b98f01a) and the freshness constants in the freshness-commitments section below — each one is re-derived from the code file cited next to it at generation time (the generator fails instead of printing a constant it cannot find in code). To regenerate this page: node scripts/gen-changelog.mjs.

what's new this week LIVE

The 10 most recent commits at generation time, across all tracks:

harvard — site & design LIVE

sprint commits from the harvard track: site pages, design, docs, SEO metros. Most recent first. Every entry cites the commit it came from.

chatbot — conversational ai LIVE

sprint commits from the chatbot track: chat UI, ranking, lists integration. Most recent first. Every entry cites the commit it came from.

data depth — engine & data LIVE

sprint commits from the data-depth track: county ingestions, engine work. Most recent first. Every entry cites the commit it came from.

signal adapter work — batches & deploys LIVE

adapter batch + archive batch commits that grew the signal catalog, and deploy checkpoints. Most recent first. Every entry cites the commit it came from.

coordination & infrastructure LIVE

everything else: coordinator notes, test maintenance, deploys, repo structure. Most recent first. Every entry cites the commit it came from.

freshness commitments — what's actually enforced by code LIVE

Every number below was re-derived from the code file cited next to it at generation time (2026-09-29). If the code changes, this section changes on the next regen — it is never hand-written. Zero freshness SLAs exist in the codebase today: no published per-signal refresh cadences, no staleness thresholds, and no refresh schedules. The timestamps and caches listed here are the entire freshness story; see data freshness for the full reference.

constantenforced valuewhat it meanscode source
PL_FRESHNESS_THRESHOLD_DAYS30purchased-list parcel records: a record older than 30 days since its last browser-local sync is honestly marked "stale"; records never synced are reported as never-synced, never given an invented dateapps/poc-web/public/assets/purchased-lists.js (plFreshnessV1)
PARCEL_CACHE_TTL3600 seconds (1 hour)/api/engine parcel cache: underlying parcels may be up to an hour older than the run's retrieved_atapps/poc-web/functions/api/engine/cache.js
engine stats cache5 minutes (CACHE_TTL_MS = 5 * 60 * 1000)in-memory cache on /api/engine/stats responsesapps/poc-web/functions/api/engine/stats.js
mcp tools/list cache60000 ms (60 seconds, server scope)the tool list is cached server-side; tools/call results are never cachedapps/poc-web/functions/lib/mcp.js (ttlMs)
/api/status edge cachepublic, max-age=60status responses may be up to 60 seconds old at the edgeapps/poc-web/functions/api/status.js
/api/intel cachecache-control: no-storeevery call re-runs the full pipeline; retrieved_at is stamped per runapps/poc-web/functions/api/intel.js
per-signal data_as_ofdeclared by exactly 1 adapter (whole_region_rank)data_as_of: epochToDate(freshestState) — the freshest upstream state date the adapter could see; every other adapter honestly ships data_as_of: nullapps/poc-web/functions/lib/signals/

planned freshness slas DRAFT

Not built, not committed, no dates. None of the following exist in code today:

how this page stays honest LIVE

next: docs hub · getting started · api reference · data freshness · error reference