docs(cache): note Java constant-route capture set in the SCHEMA_BUMP ledger

The Java constant-route harvest (route-extractors/java-const-resolver.ts +
the spring.ts operand branch + the parse-worker Java constant harvest)
changes the worker capture set: a warm pre-feature cache replays
moduleConstants=0 captures verbatim and silently drops every constant-based
Spring route on unchanged files. After rebasing onto current main the
ledger already sits at 70, whose capture set post-dates and includes this
harvest, so v70 invalidates those caches — no additional bump is needed.
This commit is contained in:
ChunxueLi 2026-08-16 20:37:20 +08:00
parent a4fc7a05f8
commit 284d587ea8

View file

@ -538,6 +538,14 @@ import type { ParseWorkerResult } from '../core/ingestion/workers/parse-worker.j
// cache would replay unchanged worker results without those routes. Version 70
// then adds Spring non-HTTP handler side-channel facts (#2417 / #2891), so Java
// and Kotlin caches persist scheduled, event, messaging, and managed-job facts.
//
// This PR originally carried its own bump (47 -> 48) for the Java constant-route
// capture set change (route-extractors/java-const-resolver.ts + the spring.ts
// operand branch + the parse-worker Java constant harvest): a warm pre-feature
// cache replays `moduleConstants=0` captures verbatim and silently drops every
// constant-based Spring route on unchanged files. After rebasing onto current
// main the ledger already sits at 70, whose capture set post-dates and includes
// this harvest — v70 invalidates those caches, so no additional bump is needed.
const SCHEMA_BUMP = 70;
const GITNEXUS_PKG_VERSION = (() => {
try {