proteum 2.2.2-1 → 2.2.3

package/docs/dev-sessions.md

@@ -1,6 +1,6 @@
 # Dev Sessions
 
-Proteum ships a dev-only auth bootstrap command so `proteum verify browser`, Playwright runs, and local debugging can start from an authenticated state without driving the login UI.
+Proteum ships dev-only auth bootstrap commands so `proteum verify browser`, `proteum e2e`, Playwright runs, and local debugging can start from an authenticated state without driving the login UI.
 
 ## When To Use It
 
@@ -31,10 +31,18 @@ proteum session admin@example.com --role ADMIN --port 3101
 proteum session god@example.com --role GOD --url http://localhost:3102 --json
 ```
 
+Playwright wrapper mode:
+
+```bash
+proteum e2e --port 3101 --session-email admin@example.com --session-role ADMIN tests/e2e/features/admin.spec.ts
+proteum e2e --url http://localhost:3101 --env FEATURE_FLAG=true --grep smoke
+```
+
 Behavior:
 
 - local mode refreshes generated artifacts, builds the dev output, starts a temporary local dev server, creates the session, prints the payload, and exits
 - remote mode talks to an already running `proteum dev` instance
+- `proteum e2e` talks to an already running `proteum dev` instance when `--session-email` is present, then starts Playwright with `E2E_BASE_URL`, optional `E2E_PORT`, optional `E2E_AUTH_TOKEN`, and any explicit `--env` or `--env-file` values in the child process environment
 - the command requires an explicit email and optionally asserts a role before returning the session
 - the command is available only in dev mode
 - browser verification flows should keep browser state app-local and disposable through `proteum verify browser` or direct Playwright instead of reusing a shared temp profile
@@ -68,7 +76,7 @@ curl -H "$(jq -r '.curlCookieHeader' session.json)" http://localhost:3101/api/Au
 ## Agent Guidance
 
 - Prefer `proteum session` over UI login automation when the goal is to test or debug protected application behavior.
-- Prefer `proteum verify browser` for focused browser-visible verification. When lower-level control is required, use direct Playwright with a disposable profile.
+- Prefer `proteum verify browser` for focused browser-visible verification, and `proteum e2e --port <port>` for targeted or full Playwright suites. When lower-level control is required, use direct Playwright with a disposable profile.
 - Use UI login automation only when the auth UX itself is the feature under test.
 - Pair it with `proteum diagnose` for a fast protected-route summary, `proteum perf request` for a one-request timing breakdown, then use `proteum trace` when you need lower-level request events.
 - Only the final verifier agent should usually run browser flows. Earlier agents should stay on `orient`, `verify owner`, `verify request`, and request-level diagnostics unless browser execution is required.
@@ -78,6 +86,7 @@ Typical flow:
 ```bash
 proteum orient /dashboard
 proteum session admin@example.com --role ADMIN --port 3101 --json > session.json
+proteum e2e --port 3101 --session-email admin@example.com --session-role ADMIN tests/e2e/features/dashboard.spec.ts
 proteum diagnose /dashboard --hit /dashboard --port 3101
 proteum perf request /dashboard --port 3101
 proteum trace latest --port 3101

package/docs/diagnostics.md

@@ -53,6 +53,7 @@ proteum diagnose /api/Auth/CurrentUser --url http://127.0.0.1:3101
 proteum verify owner /api/Auth/CurrentUser
 proteum verify request /dashboard --port 3101
 proteum verify browser /dashboard --port 3101 --session-email admin@example.com --session-role ADMIN
+proteum e2e --port 3101 --session-email admin@example.com --session-role ADMIN tests/e2e/features/dashboard.spec.ts
 
 proteum perf top --since today
 proteum perf request /dashboard --port 3101
@@ -210,7 +211,7 @@ For AI coding agents or automation:
 2. Read `./.proteum/manifest.json` or run `proteum explain --json` only after you know which surface matters.
 3. Run `proteum doctor --json` and `proteum doctor --contracts --json` to inspect framework and generated-artifact diagnostics.
 4. Use `proteum verify owner <query>` or `proteum diagnose <path> --port <port>` for the smallest trustworthy runtime surface before broad checks.
-5. Use `proteum verify browser` for browser-visible verification, and only drop to direct Playwright when request-level verification cannot reproduce the issue. Keep auth sourced from `proteum session`, and reserve browser flows for the final verifier agent unless they are the only trustworthy surface.
+5. Use `proteum verify browser` for browser-visible verification, or `proteum e2e --port <port>` for targeted/full Playwright suites. Only drop to direct Playwright when the Proteum wrapper cannot express the needed control. Keep auth sourced from Proteum session helpers, and reserve browser flows for the final verifier agent unless they are the only trustworthy surface.
 6. For performance, CPU, SQL, render, cache, or connected-boundary questions, use `proteum perf request <requestId|path>` against the same running dev server.
 7. Use `proteum trace ...` when you need lower-level event detail than `diagnose` or `perf` provides.
 8. Run global checks second, not first. Unrelated diagnostics should remain visible but non-blocking during focused verification unless strict global mode is required.

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "proteum",
 	"description": "LLM-first Opinionated Typescript Framework for web applications.",
-	"version": "2.2.2-1",
+	"version": "2.2.3",
 	"author": "Gaetan Le Gac (https://github.com/gaetanlegac)",
 	"repository": "git://github.com/gaetanlegac/proteum.git",
 	"license": "MIT",

package/scripts/update-codex-agents.ts

@@ -6,7 +6,7 @@
 import path from 'path';
 
 // Core
-import { configureProjectAgentSymlinks } from '../cli/utils/agents';
+import { configureProjectAgentInstructions } from '../cli/utils/agents';
 
 /*----------------------------------
 - TYPES
@@ -31,5 +31,5 @@ for (const projectRoot of projectRoots) {
     }
 
     console.log(`[update-codex-agents] Syncing project Codex assets in ${projectRoot}`);
-    configureProjectAgentSymlinks({ appRoot: projectRoot, coreRoot: proteumRoot });
+    configureProjectAgentInstructions({ appRoot: projectRoot, coreRoot: proteumRoot });
 }