chore: keep knip green while the mint-flag plumbing is unconsumed

The mint-kind resolver and the shared mint-kind type are both dead code until
the commits that wire them up land. Knip is right to flag them.

The webapp module joins the ignore list beside runOpsMintShard.server.ts, which
sits there for the same reason. The engine type takes a @knipignore tag, since
that package has no ignore block.

Both come back out when their consumers land.

Author: d-cs

internal-packages/run-engine/src/engine/waitpointCoordinator/types.ts

@@ -46,6 +46,8 @@ export type WaitpointCoordinator = {
  * WaitpointMintKind; re-declared because the engine never imports from the webapp.
  *
  * Read at the mint and never again — every later operation routes by the minted id's shape.
+ *
+ * @knipignore consumed by the mint-flag wiring commits later in this stack.
  */
 export type WaitpointMintKind = "legacy" | "store";
 

knip.json

@@ -26,7 +26,10 @@
         "app/v3/otlpTransformWorker.ts"
       ],
       "ignoreDependencies": ["@sentry/cli", "assert", "util"],
-      "ignore": ["app/v3/runOpsMigration/runOpsMintShard.server.ts"]
+      "ignore": [
+        "app/v3/runOpsMigration/runOpsMintShard.server.ts",
+        "app/v3/waitpointMigration/waitpointMintKind.server.ts"
+      ]
     },
     "internal-packages/dashboard-agent": {
       "entry": ["trigger.config.ts", "src/investigation-sweep.ts", "src/maintenance.ts"],