docs(qa): correct two dogfood headers that still state ADR-0094's retired 2026-07-14 overlay direction (#7351)

Both suites already pin the post-#6483 refusal correctly in their test bodies,
which carry the #6483 annotations. Only the file headers still described the
2026-07-14 direction — "a data-plane edit is TRANSLATED into an env-scope
ADR-0005 overlay" and "delete RESETS to the declared body" — as current. That
direction was retired on 2026-08-09 by ADR-0094 D5-R (#6858 / PR #6962), after
#6483 / PR #6608 rolled `permission` back to `allowOrgOverride: false`.

Prose only: the diff touches comment lines exclusively, no assertion and no
behaviour changes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016pY4Xb2iDecfDtT3CWoiTW

Author: claude

packages/qa/dogfood/test/showcase-permission-projection.dogfood.test.ts

@@ -18,8 +18,11 @@
 //      type; ADR-0086 two-doors applies meanwhile (edit the package,
 //      re-publish).
 //   3. Deleting a runtime-only set retires its record; deleting an
-//      artifact-backed set RESETS it to the declared body (the definition
-//      ships with the app and cannot be removed from the environment).
+//      artifact-backed set never removes it — the definition ships with the
+//      app and cannot be removed from the environment. Since #6483 there is
+//      no overlay left to lift, so that "reset" is a no-op success, not the
+//      revert-to-the-declared-body step ADR-0094's 2026-07-14 direction
+//      described (retired by D5-R).
 //   4. [#6483 inverted this pin too] An environment-door metadata save that
 //      targets a package-owned, artifact-backed set is refused the same way —
 //      record, provenance and effective body all stay exactly as shipped.

packages/qa/dogfood/test/two-doors-permission.dogfood.test.ts

@@ -9,11 +9,18 @@
 //        `package_id` (publish-time, not just at boot). A draft alone
 //        materializes nothing — only publish makes it live.
 //
-//  块2 — the ADMIN door (evolved by ADR-0094, direction 2026-07-14): a
-//        data-plane edit of a package-managed row is TRANSLATED into an
-//        env-scope metadata OVERLAY (the standard ADR-0005 customization) —
-//        the record projects the effective body while the package keeps
-//        owning the row, and "delete" resets to the shipped declaration.
+//  块2 — the ADMIN door (evolved by ADR-0094; its 2026-07-14 "translate the
+//        edit into an env-scope ADR-0005 overlay" direction was RETIRED on
+//        2026-08-09 — see ADR-0094 D5-R): a data-plane edit of a
+//        package-managed, ARTIFACT-BACKED row is REFUSED with 403
+//        `not_overridable` and no overlay is minted — #6483 rolled
+//        `permission` back to `allowOrgOverride: false`, and ADR-0086 names
+//        the supported channel instead: edit the package and re-publish.
+//        A "delete" through this door still degrades to a RESET — a packaged
+//        definition can never be removed from the environment — though with
+//        no overlay left to lift there is nothing for it to revert. A set
+//        authored through the data door rides the still-open
+//        `allowRuntimeCreate` tier and stays editable.
 //        Forging package provenance through the admin door stays refused.
 
 import { describe, it, expect, beforeAll } from 'vitest';