perlsky is a Perl 5 implementation of an AT Protocol Personal Data Server.
Refresh audit docs for applyWrites suite rename
+3
-3
+3
-3
docs/TEST_AUDIT.md
+3
-3
docs/TEST_AUDIT.md
···
143
143
| `t/email-confirmation.t` | audited local regression | intentionally testing-friendly email flow plus strict missing-email and invalid-email validation semantics |
144
144
| `t/email-update-helper.t` | audited local regression | shared email-update helper normalization, token revocation, and duplicate-email error semantics |
145
145
| `t/event-stream.t` | audited local regression | wire-format, malformed frame, and event decoding coverage |
146
-
| `t/extended-api.t` | audited local regression | focused `applyWrites` happy-path and missing-delete behavior after the self-service invite, identity/email, label, and blob/sync happy paths were split out |
146
+
| `t/applywrites-surfaces.t` | audited local regression | focused `applyWrites` happy-path and missing-delete behavior after the self-service invite, identity/email, label, and blob/sync happy paths were split out |
147
147
| `t/external-handle-update.t` | audited local regression | external-handle update semantics, including DID-resolution checks and empty-body success for external handle adoption |
148
148
| `t/external-surface.t` | audited local regression | focused external-surface coverage for repo/blob export and missing-blob behavior after splitting discovery, label RPC, and account-status checks into dedicated suites |
149
149
| `t/firehose.t` | audited local regression | repo subscription lifecycle, cursor, and CAR behavior |
···
185
185
186
186
The broadest suites are green and audited, but a small number still mix several categories of behavior inside the same file:
187
187
188
-
- `t/extended-api.t`
188
+
- `t/applywrites-surfaces.t`
189
189
Carries real conformance value for `applyWrites`, but it is now much narrower and mostly acts as a focused repo-write regression suite.
190
190
- `t/external-surface.t`
191
191
Carries strong external-surface coverage for repo/blob export and missing-blob listing. It is cleaner after moving discovery, label-RPC, and account-status checks into dedicated suites, but still remains broader than a single-endpoint conformance file.
···
211
211
4. decide whether to tighten admin auth to reference semantics or document the bearer shortcut as a permanent extension
212
212
5. keep local testing-only toggles, like the email-confirmation bypass, pinned in focused suites instead of letting broad mixed suites depend on them implicitly
213
213
6. keep narrowing the local `ServiceProxy` surface until every locally answered `app.bsky.*` field is either authoritative or explicitly documented as a local-only extension
214
-
7. keep documenting broad suites like `t/extended-api.t` and `t/external-surface.t` as mixed conformance-plus-product coverage rather than over-claiming that every assertion is a pure reference check
214
+
7. keep documenting broad suites like `t/applywrites-surfaces.t` and `t/external-surface.t` as mixed conformance-plus-product coverage rather than over-claiming that every assertion is a pure reference check
215
215
216
216
## Practical Reading Of The Current Status
217
217