docs: cite shareable-artifact-design as the generalized upstream doctrine

[kyle-sexton]

Summary

PLUGIN-PHILOSOPHY's design boundary is the plugin specialization of the org-wide convention now owned by melodic-software/standards conventions/engineering/shareable-artifact-design.md (standards #237, merged in standards PR #238). The design boundary states the specialization relationship; the authoritative references gain the explicit entry. Completes the follow-up promised in #933's companion work.

No linked issue: the tracked items (#933, standards#237) are already closed by their own PRs; this is their promised follow-up citation.

Related

• Add shareable-artifact-design convention: consumer-facing design doctrine for any shareable artifact standards#237 — the convention doc this cites (closed by standards PR chore: sync standards components #238; not closed by this PR).
• fleet: prefer a cross-vendor advisor at fresh-eyes checkpoint sites, presence-gated with fresh-context fallback #933 — the advisor-escalation work this citation follow-up was sequenced after (already closed by feat: prefer a cross-vendor advisor at fresh-eyes checkpoint sites fleet-wide #934).

🤖 Generated with Claude Code

[claude]

Claude finished @kyle-sexton's task in 1m 3s —— View job

---

PR Review

• Gather context
• Read changed file
• Review PR changes
• Post findings

---

This is a focused docs-only PR: two additions to docs/PLUGIN-PHILOSOPHY.md that wire in melodic-software/standards conventions/engineering/shareable-artifact-design.md as the upstream source of the design doctrine this document specializes.

Blocking checks (per REVIEW.md): all N/A — no code paths, no secrets, no authorization surface, no shared state writes.

Design boundary addition (lines 14–17)

The paragraph extension reads cleanly and accurately captures the specialization relationship. The enumeration of what the upstream doctrine covers ("consumer-agnostic behavior, externalized consumer-varying configuration, consumer tiers, explicit adoption") is precise and consistent with the sections lower in the document.

Authoritative references addition (lines 391–393)

The new bullet follows the same format as the adjacent internal melodic-software/standards reference. The entry's description — "the artifact-agnostic consumer-facing design doctrine the design boundary, configuration ownership, and setup contract above specialize for plugins" — is accurate, though the participial phrase reads slightly awkwardly (the subject "the design boundary, configuration ownership, and setup contract above" acting as the agent of "specialize" rather than "this document specializes them"). The meaning is unambiguous in context, so this is a nit, not a defect.

🟡 Nit — The reference entry's description could be rephrased for clarity:

...design doctrine that the design boundary, configuration ownership, and setup contract above **each** specialize for Claude Code plugins.

or more directly:

...design doctrine; PLUGIN-PHILOSOPHY specializes it for Claude Code plugins across its design boundary, configuration ownership, and setup contract sections.

No functional concern; either phrasing would be fine.

---

Overall: No issues. The PR is accurate, tightly scoped, and consistent with the document's existing style and reference conventions. The follow-up from #933 is properly closed out.