test(knowledge-fs): track query image migration

knowledge-fs/.harness/changes/2026-09-02-migration-runner-query-image-baseline.md

@@ -0,0 +1,24 @@
+# Include answer-trace query images in the migration-runner baseline
+
+## What changed
+
+- Added `0049_answer_trace_query_images` to the adapters migration-runner test's ordered migration baseline.
+- Kept replay and TiDB preflight fixtures derived from that shared baseline.
+
+## Why
+
+The new migration was correctly discovered by the runtime, but the explicit test baseline still ended at
+`0048_deletion_active_scope_indexes`, so migration-runner tests treated `0049_answer_trace_query_images`
+as unexpectedly pending.
+
+## Verification
+
+- `pnpm --filter @knowledge/adapters test -- src/migration-runner.test.ts`: passed.
+- `git diff --check`: passed.
+
+The repository-wide check, build, lint, and coverage gates were left to CI because this correction only
+updates the intentionally explicit migration test fixture.
+
+## Risks and follow-up
+
+- No runtime behavior changes. Future migrations must continue to update this reviewed ordered baseline.

knowledge-fs/packages/adapters/src/migration-runner.test.ts

@@ -56,6 +56,7 @@ const qualityReplayMatchPolicyMigrationId = "0045_quality_replay_match_policy";
 const removeProviderSyncPolicyMigrationId = "0046_remove_provider_sync_policy";
 const parseArtifactCheckpointsMigrationId = "0047_parse_artifact_checkpoints";
 const deletionActiveScopeIndexesMigrationId = "0048_deletion_active_scope_indexes";
+const answerTraceQueryImagesMigrationId = "0049_answer_trace_query_images";
 const migrationsAfterDurableDeletion = [
   versionedSpaceProfilesMigrationId,
   profilePublicationBindingsMigrationId,
@@ -88,6 +89,7 @@ const migrationsAfterDurableDeletion = [
   removeProviderSyncPolicyMigrationId,
   parseArtifactCheckpointsMigrationId,
   deletionActiveScopeIndexesMigrationId,
+  answerTraceQueryImagesMigrationId,
 ] as const;
 const migrationsAfterTidbBaselineRepair = [
   spaceAccessControlMigrationId,