Producer-owned path metadata for cross-layer file references

Summary#

When one layer emits only a partial file reference, every downstream consumer starts guessing hidden storage rules and those guesses diverge over time. The durable fix is to have the producer emit a canonical, self-describing reference format so UI, upload, and automation paths all resolve the same artifact without special cases.

Problem#

A node saved assets under a temp directory but exposed only a bare filename, forcing frontend and cloud upload code to infer the real location differently and breaking previews.

Solution#

Make the producing component include standardized location annotations such as folder type in its output contract, and require consumers to follow that shared convention instead of repo-specific heuristics.

Failure Modes#

Consumers keep fallback inference logic and drift again later.
Only one producer is fixed, leaving other emitters with ambiguous references.
The annotation format is undocumented or inconsistently serialized.

Sources#

https://github.com/Comfy-Org/ComfyUI/pull/16038
https://github.com/Comfy-Org/ComfyUI/pull/16024
https://github.com/Comfy-Org/ComfyUI/pull/16025
https://github.com/Comfy-Org/ComfyUI/pull/16014
https://github.com/Comfy-Org/ComfyUI/pull/16020
https://github.com/GitHubDaily/GitHubDaily/pull/267
https://github.com/GitHubDaily/GitHubDaily/pull/52
https://github.com/react/react/pull/37305
https://github.com/react/react/pull/37355
https://github.com/react/react/pull/37376
https://github.com/react/react/pull/37366
https://github.com/react/react/pull/37475
https://github.com/react/react/pull/37457
https://github.com/react/react/pull/37465
https://github.com/thedaviddias/Front-End-Checklist/pull/737
https://github.com/thedaviddias/Front-End-Checklist/pull/664
mined_at: 2026-09-02T12:31:39Z

Sagwan Revalidation 2026-09-02T13:09:51Z#

verdict: ok
note: 일반 설계 원칙 중심이라 최신 practice와 충돌 없이 재사용 가능.

Sagwan Revalidation 2026-09-08T16:11:28Z#

verdict: ok
note: [chatgpt HTTP 404] {

Sagwan Revalidation 2026-09-11T05:07:22Z#

verdict: ok
note: 일반 원칙 중심이라 최근 관행과 충돌 없고 재사용 가능함

Sagwan Revalidation 2026-09-14T00:36:29Z#

verdict: ok
note: 생산자가 정규 위치 메타데이터를 직접 포함해야 한다는 원칙은 시대를 타지 않고, GitHub PR 링크는 영구적으로 유효하다.