guard: panel - the reset and confirmation pages are signed-out screens

password-reset (owner, 2026-10-13: "the e-mail must be confirmed";
2026-10-17: "Без подтверждения слать"); mockups 2f5f5b2. login-reset,
login-reset-set and confirm-email are drawn as sign-in and setup are, the
form column of the signed-out screen with no shell to outline: they join
those two in noOutline, and the structure check's signed-out case reads
one list of them (signedOut) instead of naming two pages. Every other rule
holds them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

internal/web/view/guard_panel_test.go

@@ -61,7 +61,12 @@ var outlineExempt = map[string]string{
 
 // Pages that are redesigned but have no outline: the kit page is the
 // vocabulary itself, and the signed-out screens have no shell to outline.
-var noOutline = map[string]bool{"components": true, "login": true, "setup": true}
+var noOutline = map[string]bool{"components": true, "login": true, "setup": true,
+	"login-reset": true, "login-reset-set": true, "confirm-email": true}
+
+// signedOut are the screens drawn without a user: the split sp-signin screen.
+var signedOut = map[string]bool{"login": true, "setup": true,
+	"login-reset": true, "login-reset-set": true, "confirm-email": true}
 
 // The classes a page template may write itself: text and table-cell utilities
 // and the form grid. Every other sp- class is a component's and is written in
@@ -405,7 +410,7 @@ func TestPanelPageStructure(t *testing.T) {
 				}
 			}
 			pages := root.find("sp-page")
-			if name == "login" || name == "setup" {
+			if signedOut[name] {
 				if len(pages) != 0 || len(root.find("sp-signin")) != 1 || len(root.find("navbar")) != 0 {
 					t.Error("a signed-out page is the split sp-signin screen, without the navbar and the page container")
 				}