Improve developer forge extension surfaces

ARCHITECTURE.md

@@ -73,8 +73,10 @@ The frontend lives under `frontend/` and is a Vite Vue SPA.
 
 The shell owns navigation, route handling, auth/session exchange, GraphQL
 transport, extension UI loading, core widgets, and shared layout. Extension UI
-bundles are browser ESM assets served from `/_extensions/<id>/assets/...` and
-loaded through the SDK registry.
+bundles are browser ESM assets served from
+`/forge-ui/<module-token>/files/...` and loaded through the SDK registry.
+The module token is the hex-encoded extension ID used only for public asset
+URLs.
 
 Route ownership:
 

GOAL.md

@@ -25,7 +25,7 @@ Status: v3 cutover complete; read/write transport split is the north star
   graph after SP6 lands.
 - The Vue/Vite shell is the only frontend.
 - Extension UI bundles are generated from the `ui/` sources and served from
-  `/_extensions/...`.
+  `/forge-ui/...`.
 - `start.sh --reset --oneshot` is the end-to-end acceptance path.
 
 Do not restore removed transition routes, old GraphQL aliases, resolver stubs,

PRODUCTION_TESTBED.md

@@ -84,9 +84,9 @@ storage paths are absolute.
 - `POST /events/session`
 - `GET /events`
 - `GET /graphql/stream`
-- `POST /_extensions/session`
-- `GET /_extensions/<id>/manifest.json`
-- `GET /_extensions/<id>/assets/<path>`
+- `POST /forge-ui/session`
+- `GET /forge-ui/<module-token>/meta.json`
+- `GET /forge-ui/<module-token>/files/<path>`
 - `/git/...` authentication and scope checks
 
 ## Current production-testbed boundary

README.md

@@ -56,7 +56,9 @@ Rust `cargo-component` crates and ship real artifacts at
 
 The Vue shell owns navigation, auth/session exchange, GraphQL transport, and UI
 extension loading. Browser extension bundles are served from
-`/_extensions/<id>/assets/...` and registered through the Comtrya SDK.
+`/forge-ui/<module-token>/files/...` and registered through the Comtrya SDK.
+The module token is the hex-encoded extension ID used only for public asset
+URLs.
 
 Git clone/fetch uses the pure-Rust Smart HTTP path. Git receive-pack/push and
 full OIDC browser callback validation are intentionally unsupported in the

SPEC.md

@@ -23,7 +23,7 @@ feature behavior delivered by WASM extensions.
   SP6 lands. The `/api/ops` surface is interim; do not extend it beyond what
   current extensions need.
 - The frontend is a Vite/Vue shell that loads extension UI bundles from
-  `/_extensions/...`. The shell uses GraphQL for reads and RPC for writes;
+  `/forge-ui/...`. The shell uses GraphQL for reads and RPC for writes;
   extension UI bundles follow the same contract via the generated SDK.
 - The implementation favors deletion and current contracts over transition
   layers.

TODO.md

@@ -16,7 +16,7 @@ Comtrya product.
   previews, and diffs derived from Git.
 - Real: Git clone/fetch works through the Vue origin using a scoped Comtrya
   credential.
-- Real: extension UI manifests and assets are served from `/_extensions/...`.
+- Real: extension UI manifests and assets are served from `/forge-ui/...`.
 - Real: the Vue shell discovers installed extensions, validates UI manifests,
   imports versioned entry assets, and mounts slot/route contributions.
 - Real: first-party backend extensions are Rust `cargo-component` crates that

comtrya.cue

@@ -22,8 +22,11 @@ repository: schema.#Repository & {
 	// inherit this enablement; per-project `issues` / `epics` blocks
 	// are policy defaults, not feature toggles. ext_epics is listed so
 	// project epics and issue-to-epic relationships are available to
-	// every project in this repo.
-	extensions: ["ext_issues", "ext_pull_requests", "ext_checks", "ext_epics"]
+	// every project in this repo. ext_docs is listed so project-owned
+	// ADRs, specs, PRDs, and BDD scenarios render through the repository
+	// docs surface instead of living as untyped files. ext_sprints turns
+	// sprint planning into a first-class repo workbench surface.
+	extensions: ["ext_issues", "ext_pull_requests", "ext_checks", "ext_epics", "ext_docs", "ext_sprints"]
 
 	bookmarks: [
 		{
@@ -93,6 +96,29 @@ projects: backend: {
 				status: "string"
 			}
 		}
+		prd: {
+			slug:        "server/docs/prds"
+			label:       "Backend PRDs"
+			description: "Product requirements for backend-owned forge capabilities."
+			properties: {
+				title:    "string"
+				owner:    "principal-ref"
+				status:   "string"
+				audience: "string"
+			}
+		}
+		scenario: {
+			slug:        "server/docs/scenarios"
+			label:       "BDD Scenarios"
+			description: "Behavior scenarios that describe user-visible forge workflows."
+			properties: {
+				title:   "string"
+				feature: "string"
+				owner:   "principal-ref"
+				status:  "string"
+				tags:    "[...string]"
+			}
+		}
 	}
 
 	pulls: {
@@ -111,6 +137,11 @@ projects: backend: {
 		requiredFields: ["title"]
 	}
 
+	sprints: {
+		cadence:         "weekly"
+		defaultCapacity: 8
+	}
+
 	checks: {
 		catalog: {
 			"cargo test": {

crates/core/src/extensions.rs

@@ -50,7 +50,7 @@ pub struct ExtensionInstallConfig {
 /// already rejects any prefix starting with `_` — the entry was permanently
 /// unreachable and only existed as defensive documentation (#122 P3).
 pub const RESERVED_ROUTE_PREFIXES: &[&str] = &[
-    "r", "x", "api", "auth", "git", "graphql", "events", "readyz", "healthz", "instance",
+    "r", "x", "api", "auth", "git", "graphql", "events", "readyz", "healthz", "instance", "ui-ext",
 ];
 
 fn validate_route_prefix(prefix: &str) -> CoreResult<()> {

crates/core/src/http.rs

@@ -36,11 +36,11 @@ pub fn allowed_methods_for_route(route: &str) -> Vec<&'static str> {
     match route {
         "/graphql" => vec!["GET", "POST", "OPTIONS"],
         "/graphql/stream" | "/events" => vec!["GET", "OPTIONS"],
-        "/events/session" | "/auth/token-exchange" | "/_extensions/session" => {
+        "/events/session" | "/auth/token-exchange" | "/ui-ext/session" => {
             vec!["POST", "OPTIONS"]
         }
         route if route.starts_with("/auth/") => vec!["GET", "POST", "OPTIONS"],
-        route if route.starts_with("/_extensions/") => vec!["GET", "OPTIONS"],
+        route if route.starts_with("/ui-ext/") => vec!["GET", "OPTIONS"],
         route if route.starts_with("/api/ops/") => vec!["POST", "OPTIONS"],
         // `/r/<repo>` multiplexes browse (GET) and git smart-HTTP
         // (GET info/refs, POST upload-pack/receive-pack) under one prefix,

crates/server/docs/prds/repository-docs-surface.mdx

@@ -0,0 +1,36 @@
+---
+title: Repository Docs Surface
+owner: platform-maintainers
+status: active
+audience: maintainers
+---
+
+## Problem
+
+Developers expect a forge to keep product intent beside the implementation. Comtrya
+already stores ADRs and specs in the repository, but product requirements and
+scenario-style acceptance criteria need the same first-class surface so a
+single-tenant forge can connect planning, implementation, and review without
+sending users to a separate product tool.
+
+## Requirements
+
+- A repository can opt into `ext_docs` once and expose project-owned document
+  types from `comtrya.cue`.
+- Backend-owned PRDs live under `crates/server/docs/prds/` and render in the
+  Docs extension with their declared front matter.
+- Scenario documents live beside backend docs and describe user-visible
+  workflows in a format that can later drive tests or issue templates.
+- The kernel stays generic: it evaluates doc type shape from CUE, while
+  `ext_docs` owns the reading and rendering experience.
+
+## Non-Goals
+
+- Do not hardcode PRD or BDD semantics into the kernel.
+- Do not add a separate requirements service before repo-resident docs have
+  been proven in the main forge workflow.
+
+## Success
+
+Opening the backend project docs shows ADRs, specs, PRDs, and BDD scenarios as
+declared document types, each backed by real repository files.

crates/server/docs/scenarios/repository-docs-surface.mdx

@@ -0,0 +1,22 @@
+---
+title: Repository docs are discoverable from project context
+feature: repository-docs
+owner: platform-maintainers
+status: active
+tags: [docs, projects, bdd]
+---
+
+## Scenario
+
+Given the Comtrya repository has opted into `ext_docs`
+And the backend project declares ADR, spec, PRD, and scenario document types
+When a developer opens the repository docs surface
+Then the docs panel groups documents by backend project and declared type
+And each file shows its front matter, path, and rendered MDX body
+And the developer can expand a document without leaving the forge shell.
+
+## Notes
+
+This scenario is intentionally stored as MDX today. The shape is simple enough
+for humans to review, and it gives the extension a concrete BDD-style artifact
+to render before we invest in a stricter Gherkin parser or test generator.