From 65aadcb38ad0040ca2f91f84935cb2ce46991d6a Mon Sep 17 00:00:00 2001
From: Filippo Venturini <73821401+Filippo-Venturini@users.noreply.github.com>
Date: Fri, 14 Nov 2025 11:06:10 +0100
Subject: [PATCH] docs(upscale-metadata): propose options for exposing original
 image metadata

---
 .../util/graph/buildMultidiffusionUpscaleGraph.ts     | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/invokeai/frontend/web/src/features/nodes/util/graph/buildMultidiffusionUpscaleGraph.ts b/invokeai/frontend/web/src/features/nodes/util/graph/buildMultidiffusionUpscaleGraph.ts
index 26db510599c..b003b2779ab 100644
--- a/invokeai/frontend/web/src/features/nodes/util/graph/buildMultidiffusionUpscaleGraph.ts
+++ b/invokeai/frontend/web/src/features/nodes/util/graph/buildMultidiffusionUpscaleGraph.ts
@@ -178,6 +178,17 @@ export const buildMultidiffusionUpscaleGraph = async (state: RootState): Promise
 
   const modelConfig = await fetchModelConfigWithTypeGuard(model.key, isNonRefinerMainModelConfig);
   const upscaleModelConfig = await fetchModelConfigWithTypeGuard(upscaleModel.key, isSpandrelImageToImageModelConfig);
+  
+// DISCUSSION: Currently we store only a reference to the original image
+// via `upscale_initial_image`. The full metadata of the source image
+// (prompt, seed, scheduler, etc.) is not included here. 
+//
+// Two options could be considered:
+// 1) Expose a UI way to jump to the source image in the gallery (leveraging this reference).
+// 2) Store all original image metadata under a separate field (e.g., `source_image_metadata`) 
+//    for external or export use.
+//
+// This PR is meant to discuss which approach is preferred before implementing.
 
   g.upsertMetadata({
     cfg_scale,