Add public breach/termination record to TRSL V1C1 §7 (Trust Service)

Per maintainer request after reviewing V1C1: breaches and their resolution
are transparently published via the Trust Service, giving the ecosystem a
conformity signal and creating reputational pressure toward compliance
alongside the existing commercial remedies.

- V1C1 §7.4 (new): Trust Service publishes the Licensor's breach notices,
  cure status, and termination determinations per Phase, distinguishing
  "alleged" from "determined" — a ministerial recording act, not a new
  discretionary authority (consistent with §5.4's evidence-not-cause
  principle). Named-by-default disclosure is the intended mechanism (the
  deterrent only works if the party is identifiable), flagged in Appendix A
  item 10 as the single most legally sensitive addition in this candidate:
  it touches Commercial Use Agreement confidentiality, defamation law, and
  data-protection law where the affected party is an individual.
- TSD §4.1: new Breach/Compliance Record Trust Service component, noted as
  license-driven and deferred to a future Trust Service PRD rather than
  retrofitted into WP-0002's already-finished Stage 0 scope.
- OpenQuestions-WorkingDefaults.md Q12: records the adopted default (publish
  alleged/determined breach status) and the still-open naming-policy question.
- PRD FR-10: cross-references the new public record without resolving the
  naming question.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

workplans/TREV-WP-0001-license-prior-art-research.md

@@ -234,3 +234,15 @@ ready for human review, not accepted.** Task should be marked `done` only
 after a maintainer confirms V1C1 is adequate briefing material for counsel
 (the deliverable this task now points to; the archived skeleton is
 superseded, not the current target of the human-accept gate).
+
+Result 2026-07-29 (maintainer review): maintainer reviewed V1C1 ("quite
+strong") and requested one addition to §7 — public Trust Service
+publication of breach notices, cure status, and termination
+determinations, for ecosystem-signal/conformity-pressure purposes. Added as
+new §7.4, with a naming-by-default mechanism (identifies the affected
+party unless confidentiality/legal constraints require otherwise) flagged
+as the single most legally sensitive open item in the candidate (Appendix
+A item 10; `OpenQuestions-WorkingDefaults.md` Q12 item 5). Propagated to
+`specs/TechnicalSpecificationDocument.md` §4.1 (new Breach/Compliance
+Record Trust Service component) and `specs/ProductRequirementsDocument.md`
+FR-10. Still `todo` — ready for continued human review.