[HackTuah]

The slice/062 tag fired the package workflow for the first time over slice 062, and all three
legs failed to compile the release (run 35786247006, linux / macOS / windows, one cause):

== Compilation error in file lib/trinity_web/endpoint.ex ==
** (ArgumentError) cannot escape #Function<0.132933281/1 in Trinity.MCP.Server.Plug.init/1>.

Plug.Builder calls a plug's init/1 at compile time when MIX_ENV=prod and escapes the result
into the compiled endpoint. Slice 062 replaced 061's authorize: &Auth.Local.authorize/1 with an
anonymous function closing over the process-dictionary key; a closure cannot be escaped. The hook is
now &__MODULE__.authorized/1, a public function with the same body and a typespec.

Nothing about the authorization behaviour changes: call/2 still authorizes before the transport
runs and the hook is still the transport's second look at what it decided.

• Regression test: test/trinity/mcp/server_test.exs, "every option the plug's init returns can be
  escaped, as a compile-time init must be" — it runs Macro.escape/1 over Plug.init([]), the
  compile-time step that failed, and was demonstrated red against the closure with the same message
  CI printed.
• Verified: MIX_ENV=prod mix compile exits 0 on this branch and exits 1 on main at 9859fbe.
• Records: slice 062's NOTES.md (F5, with the reproduction) and PROOF.md carry appended
  corrections; neither is rewritten and the tag is not moved.

Follow-up for the owner, in NOTES: nothing in mix gate or the push-triggered CI compiles
:prod, and package.yml triggers on tags only, so this class of defect is invisible until after
approval. Either a MIX_ENV=prod mix compile step in the gate or a branches: trigger on
package.yml would close it; that is the gate's contract and every slice's, so it is not changed
here.