Problem #
tang currently treats a successful PDS record write as a successful Tangled operation even when repository backlinks, the appview, or the public page have not caught up.
Acceptance criteria #
- Mutations expose distinct PDS, backlink, appview, and public visibility states.
- Human output never prints a public success that was not verified.
- JSON returns stable structured verification fields.
- Create/status commands support bounded waiting and strict required-layer failure.
- The same verification model can be reused by issues, pulls, comments, and Pages.