G-084 notes: record the shared-parsekey received-attribution display gap

parse_report's Source column and parse_status's per-arg `received` count both
report default/0 for an explicitly-supplied shared-parsekey member (e.g
parse_report {-exact ...} withid ::lsearch shows every MATCHSTYLE member as
(default) though the value is correctly bridged) - parse_status_build keys
the positions dict by the storage key, so no per-member received attribution
survives the fold. Pre-existing (G-151 bridge, G-049 attribution loop), not
introduced by G-083. Flip when the engine-level storage-key model G-084 owns
lands (the same follow-on that retires the value-bridge).

Assisted-by: harness=pi; primary-model=huggingface/zai-org/GLM-5.2; api-location=huggingface.co

goals/G-084-punkargs-parsekey-completeness.md

@@ -60,3 +60,10 @@ _GAP test in src/tests/modules/punk/args/testsuites/args/parsekey.test:
   vs definition argument names to this goal - when that lands, the display
   bridge in parse_report (and the matching miss noted in
   private::parse_status_build's comment) can retire.
+- Concrete display gap for the above: parse_report's Source column and
+  parse_status's per-arg `received` count both report `default`/0 for an
+  explicitly-supplied shared-parsekey member (e.g `parse_report {-exact ...}
+  withid ::lsearch` shows every MATCHSTYLE member as `(default)` though the
+  value is correctly bridged) - `parse_status_build` keys the positions dict by
+  the storage key, so no per-member received attribution survives the fold;
+  flip when the engine-level storage-key model lands (the same follow-on).