Dev Updates

Phase 1 prints rollout now includes a dedicated shadow backfill that hydrates one print record for each existing active card without changing any live read paths, API payloads, ingestion identity semantics, or card canonical IDs. The backfill runs in bounded batches with per-batch transactions so it can be rerun safely, resumed predictably, and executed with low operational risk while preserving existing user-facing behavior. Contract coverage was expanded to validate core safety guarantees: cards missing prints are hydrated correctly, reruns remain idempotent, pre-existing print rows are preserved without duplication, and card rows are not mutated by the hydration process. This completes the baseline shadow-data layer needed for future print-aware read evolution while keeping current production behavior stable and fully backward compatible.

Phase 1 prints scaffolding has been extended with a tightly scoped shadow dual-write step that records a print row when a new card is created, without changing existing read behavior, API outputs, ingestion identity rules, or canonical card routing. This keeps current user-facing behavior stable while increasing confidence that future print-aware phases can be introduced incrementally instead of through a risky all-at-once migration. The update also closes a timestamp consistency gap by ensuring print updates track modification time the same way as existing core models. Additional contract coverage now verifies that print creation happens once per card creation path, card updates do not duplicate print rows, delete cascade behavior remains intact, and card fields stay unchanged through the shadow write. Together these checks reinforce blast-radius containment while preserving Phase 1's behavior-neutral deployment goal.

The Phase 1 prints scaffold now includes additive ORM wiring so the existing schema can be exercised through application models without changing user-facing behavior. A new Print model has been connected to Card with explicit bidirectional relationships and cascade semantics that align with the current foreign key contract. This closes the gap between migration scaffolding and model-layer readiness while preserving current routing, ingestion, and card identity behavior. A focused relationship test contract was also introduced to verify model import availability, association linkage, and cascade delete behavior against the existing table design. The result is safer groundwork for later print-aware service phases: the codebase can now represent print records in ORM space, but no production flow has been re-routed to depend on prints yet, keeping Phase 1 behavior-neutral and deploy-safe.

Phase 1 prints scaffolding is now in place with an additive schema baseline that can support the upcoming Card plus Print identity rollout without changing current card-level behavior. The database now includes a dedicated prints structure with constrained identity fields and foreign key boundaries, while existing card ingestion and read paths remain stable. This keeps migration work incremental and lowers risk by preserving established production behavior during early scaffolding. Reliability fixes were included alongside the scaffold to prevent regression risk during validation and ingestion operations. Contract test paths now recover cleanly after expected integrity failures, test cleanup explicitly handles prints rows tied to test cards, and artifact-backed ingestion no longer depends on API-route imports for set registration status. Together these changes reduce hidden coupling, improve repeatability, and make the scaffold safer to build on in subsequent ORM and backfill phases.

A full Phase 0 pre-prints audit is now documented with query-backed evidence from local and production datasets to ground the upcoming identity migration in facts instead of assumptions. The update captures current collision frequency, duplicate guard semantics, canonical identity construction paths, API and UI coupling points, and all major attachment dependencies that currently bind pricing and sales records to card-level identifiers. This gives the team a reliable baseline for assessing migration blast radius before any behavior changes are introduced. A companion RFC draft now defines the Card (abstract) plus Print (collectible instance) target model, migration invariants, and phased rollout boundaries focused on backward compatibility. The draft explicitly scopes what can change in early phases and what must remain stable to protect routes, ingestion idempotency, and existing market data surfaces while the identity layer evolves.

A full internal identity audit is now documented to establish the current-state baseline before introducing a Card-to-Print architecture. The audit traces canonical identity creation, duplicate detection, database uniqueness rules, ingestion assumptions, and API surface expectations so teams can see exactly where identity is enforced and where behavior can collapse when variants share the same semantic key. This creates a shared source of truth for current behavior rather than inferred behavior from isolated modules. The report also maps risk and migration complexity across routing, serializers, image and pricing attachment layers, and search/index surfaces. By separating observation from implementation decisions, the system now has a concrete evidence package for planning a safe prints migration with fewer regressions, clearer backfill requirements, and explicit awareness of where compatibility and redirects will be needed.

JK Index now has a production-safe GA4 foundation aligned to the analytics audit contract, with explicit provider controls for off, GA-only, and dual-write operation. The app initializes GA4 safely in the App Router with non-blocking guards, preserves local-off defaults, and ensures analytics cannot break rendering or navigation. This establishes a clean migration path where teams can validate parity before retiring Vercel Analytics. Core high-value intent signals are now wired through a typed analytics client rather than ad hoc event calls. Card views, set views, scan completion outcomes, and homepage TCG selection are normalized into canonical events with consistent context, dedupe protection, and parameter sanitization. The result is cleaner instrumentation, better attribution quality, and a stable base for dashboards and next-phase transition events.

A complete analytics blueprint is now in place to move JK Index to GA4 as the long-term source of product truth. The audit defines all user-visible surfaces, maps route-level intent, and introduces a canonical event model focused on collector behavior across cards, sets, articles, news, tools, and account flows. This creates a shared language for measurement so teams can compare behavior consistently across TCGs and reduce drift from ad hoc event naming over time. The plan also establishes implementation guardrails for reliability and governance, including parameter standards, cardinality controls, PII safety boundaries, dual-write validation, and a practical cutover checklist from Vercel Analytics. With this structure, analytics can support decision-making directly while preserving confidence during migration and minimizing risk from duplicate tracking or noisy events.

The Latest Shipped Features card layout was refined to improve visual readability by keeping the icon and headline on a single line. This reduces visual hopping when scanning newly shipped items and makes feature cards easier to parse quickly, especially on smaller viewports where stacked title treatment felt fragmented. The update is strictly presentational and preserves existing feature selection, ordering, and visibility behavior.

Carrying On His Will (OP13) is now onboarded through the existing artifact ingestion path with production-safe guardrails, so the set can be released without introducing a new pipeline. The rollout includes explicit non-local write confirmation for artifact-driven ingestion, production verification steps for set and card integrity, and a clean handoff into existing post-ingestion flows for metadata and image enrichment.

The internal artifact-to-ingestion bridge was strengthened to improve consistency, audit clarity, and future set onboarding without changing the artifact contract or default safety posture. Set identity is now derived in a canonical, deterministic way before ingestion calls, so naming and set context remain aligned with existing platform conventions across card catalogs and reporting surfaces. This closes a trust gap where fallback identities could be technically valid but operationally inconsistent for newly introduced sets.

The JK Archivist raw-collection module is now exposed as an OpenClaw skill. Agents can invoke the skill via the dedicated route to run the read-only, one-URL-to-one-artifact flow without touching ingestion or the rest of the JK Index. The skill remains read-only; adapter and ingestion stay outside the skill boundary.