Graphify: canonical GSD artifacts retain dated and checkout-derived fields

[jodobear]

Reviewer findings

• Reviewer: GitHub Codex
• Findings:
  • docs: establish lean GSD delivery authority #38 (comment)
  • docs: establish lean GSD delivery authority #38 (comment)
• Reviewed SHA: a4d34329bc32757a6f640b565fc7da6808908636
• Severity: P2
• Locations: generated GRAPH_REPORT.md date and underscore-encoded checkout-derived phantom node IDs

Impact

Installed Graphify 0.9.13 can emit wall-clock report dates and encode checkout paths into unresolved local-import node IDs. This creates noisy canonical GSD graph diffs and can disclose local checkout naming.

Current disposition

• PR docs: establish lean GSD delivery authority #38 replaces tracked graphify-out/ runtime/cache data and custom normalization with the installed $gsd-graphify contract.
• The canonical .planning/graphs/ artifacts remain exactly skill-generated. Uzel will not patch Graphify, add a wrapper, or add another normalization pipeline.
• Classification: upstream/tooling backlog; safe P2 deferral under explicit user direction.
• Owner: Graphify/GSD integration maintainers; Uzel maintainer tracks adoption.
• Target: next installed Graphify/GSD upgrade evaluation.
• Revisit trigger: installed Graphify release or GSD graph contract change claiming portable canonical artifacts.

Observable acceptance

A fresh installed $gsd-graphify build from two differently named checkouts emits canonical graph/report artifacts with no wall-clock date, literal or encoded checkout prefix, stale/deleted phantom node, or content-only diff; status/query/diff remain usable without project-side post-processing.