From c7aeee3069b96b9ea14e2fc31397e3a866c72bc5 Mon Sep 17 00:00:00 2001 From: fylorn <249551762+fylorn@users.noreply.github.com> Date: Mon, 14 Sep 2026 15:33:35 +0800 Subject: [PATCH] docs: drop the one dangling design-doc citation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A comment in `crates/common/src/errors.rs` cited `thinkwatch-core DESIGN §9.3`, a document that exists in none of the three repositories. The same cleanup just landed in Core and Lite; this is the only site here. The sentence already carried the whole argument — the shared layer must not know this crate's error taxonomy, which is why `tw-crypto` has its own `SecretError` — so only the pointer goes. Every other section reference in this repo is left alone, because they are real: RFC 6749, 6585, 7231, 7591, 7636, 8414 and 9728, the MCP authorization spec, and `LICENSING.md §Tier Determination`, which is an actual heading in an actual file here. Co-Authored-By: Claude Opus 5 --- crates/common/src/errors.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/common/src/errors.rs b/crates/common/src/errors.rs index 9901a8ab..9138e393 100644 --- a/crates/common/src/errors.rs +++ b/crates/common/src/errors.rs @@ -134,7 +134,7 @@ impl IntoResponse for AppError { impl From for AppError { /// The shared layer must not know this crate's error taxonomy — that /// is why `tw-crypto` carries its own `SecretError` rather than - /// returning `AppError` directly (thinkwatch-core DESIGN §9.3). + /// returning `AppError` directly. /// /// A secret that will not decrypt is always `Internal`: the caller /// supplied a well-formed request, and the failure is either a wrong