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>

specs/OpenQuestions-WorkingDefaults.md

@@ -164,6 +164,8 @@ Status `canonical` requires documented review; Stage 0 may ship them as `registe
 1. Ledger is append-only; disputes create compensating entries, not silent edits.  
 2. Conversion already triggered remains irrevocable (Rule 9) even if a later dispute reduces Development Credit — shortfall is a commercial/audit matter, not re-restriction.  
 3. When the Trust Service operator is also a Phase licensor, attestations must be independently re-computable offline; public metrics must not depend on private operator judgment.  
+4. **(Added 2026-07-29, TRSL V1C1 §7.4)** Breach notices, cure status, and termination determinations for a Phase are published by the Trust Service as a public conformity signal, distinguishing `alleged` from `determined`. Publication is a ministerial record of the Licensor's (or a dispute process's) determination — the Trust Service does not itself decide whether a breach occurred.  
+5. **(Added 2026-07-29, TRSL V1C1 Appendix A item 10 — blocked on legal)** Whether the published breach record names the affected party by default (the mechanism's intended deterrent effect) or falls back to an anonymized Phase-and-category record, and how that interacts with Commercial Use Agreement confidentiality, defamation law, and data-protection law. This is the single most legally sensitive open item introduced by V1C1.
 
 **Blocked on governance:** Full dispute SLA and third-party auditor program (PRD Phase 7).