feat(surf): AssembleRouter builds the router and handler once; the router stops the MCP endpoint it mounted (quick-261118-lbt)

- surf.AssembleRouter returns the router and the compiled handler from
  one build, so an mcp.enabled app is not built twice; Assemble keeps
  its signature and is implemented on top of it
- serve uses AssembleRouter with a deferred Router.Close
- pier.Pier.Close stops the session reaper and the Redis warm-up; the
  router that mounted the endpoint owns it
- ExampleAssembleRouter, routing/testing docs and the surf/pier READMEs
This commit is contained in:
Jakub Zych
2026-11-18 15:44:56 +01:00
parent d9e21ad019
commit 38f7f3a777
11 changed files with 257 additions and 16 deletions

View File

@@ -27,7 +27,9 @@ In an application with local plugins in a `go.work` workspace, run the tests of
## Unit tests without a database
Most plugin code runs without a database. Build a container with `backpack.New`, call your plugin's Register and Boot, and assert on what it published. Drive HTTP handlers with `net/http/httptest`: `surf.Assemble` builds the same handler `serve` uses, so a test can send requests to your routes without listening on a port. Call console commands in-process with `bonfire.Call`.
Most plugin code runs without a database. Build a container with `backpack.New`, call your plugin's Register and Boot, and assert on what it published. Drive HTTP handlers with `net/http/httptest`: `surf.AssembleRouter` builds the same handler `serve` uses, together with its route table and admin prefix from one build, so a test can send requests to your routes without listening on a port; `defer r.Close()` on the returned router so its rate-limit store stops. Call console commands in-process with `bonfire.Call`.
Full-boot tests may call `t.Parallel()`: `party.Activate` gives each application its own plugin instances, so two applications booted in one test binary do not share plugin state, provided your plugin keeps its per-application state on its struct and not in package variables. Column-encryption keys are the exception: they are process-wide, and the last `lagoon.PublishEncryptionKeys` wins.
## Database tests