Point the factory result override at its removal issue

The `FactoryRunResult` override and its boundary cast are scaffolding for a
schema limitation, not a permanent part of the surface. Name the tracking issue
in both docblocks so whoever regenerates after the schema change knows exactly
what to delete.

Author: MRayermannMSFT

nodejs/src/factory.ts

@@ -23,6 +23,12 @@ import type { FactoryLimits, FactoryMeta } from "./types.js";
  * array — but the schema models the field as an opaque node, which the
  * generator renders as an object. Narrowing the correction to this surface
  * keeps the `x-opaque-json` handling unchanged for every other consumer.
+ *
+ * This override is temporary. Once the schema distinguishes an opaque JSON
+ * value from an opaque in-process value and that ships in a CLI release,
+ * regenerating produces the right type directly, and this declaration, the
+ * `toPublicFactoryRunResult` boundary helper, and the casts around it should
+ * all be deleted. Tracked by github/copilot-agent-runtime#14122.
  */
 export type FactoryRunResult = Omit<WireFactoryRunResult, "result"> & {
     /** Completed factory result. */

nodejs/src/session.ts

@@ -297,6 +297,10 @@ class FactoryProgressBuffer {
  * corrects that for the factory surface without changing `x-opaque-json`
  * handling for any other consumer, so the boundary needs a cast rather than a
  * conversion.
+ *
+ * Delete this along with the {@link FactoryRunResult} override once the schema
+ * distinguishes opaque JSON values from opaque in-process values —
+ * github/copilot-agent-runtime#14122.
  */
 function toPublicFactoryRunResult(envelope: WireFactoryRunResult): FactoryRunResult {
     return envelope as FactoryRunResult;