chore: rename npm scope to @intent-framework (#41)

Author: mahyarmlk

AGENTS.md

@@ -91,22 +91,22 @@ If implementation and docs disagree:
 The current MVP focuses on:
 
 ```txt
-@intent/core
-@intent/dom
-@intent/testing
-@intent/server
-@intent/router
+@intent-framework/core
+@intent-framework/dom
+@intent-framework/testing
+@intent-framework/server
+@intent-framework/router
 examples/web-basic
 ```
 
 Do not start these without explicit user direction:
 
 ```txt
-@intent/devtools
-@intent/openapi
-@intent/realtime
-@intent/react-native
-@intent/compiler
+@intent-framework/devtools
+@intent-framework/openapi
+@intent-framework/realtime
+@intent-framework/react-native
+@intent-framework/compiler
 complex SSR
 complex server adapters
 visual editor
@@ -123,7 +123,7 @@ Build the dagger before the cathedral.
 
 ### Core
 
-`@intent/core` must stay semantic and platformless.
+`@intent-framework/core` must stay semantic and platformless.
 
 It must not depend on:
 
@@ -171,11 +171,11 @@ React component
 
 ### DOM
 
-`@intent/dom` may depend on:
+`@intent-framework/dom` may depend on:
 
 ```txt
-@intent/core
-@intent/router
+@intent-framework/core
+@intent-framework/router
 ```
 
 It must not depend on React.
@@ -195,10 +195,10 @@ Browser DevTools should show real, inspectable DOM.
 
 ### Router
 
-`@intent/router` may depend on:
+`@intent-framework/router` may depend on:
 
 ```txt
-@intent/core
+@intent-framework/core
 ```
 
 It must preserve typed route params and service typing.
@@ -207,10 +207,10 @@ Do not make core depend on router.
 
 ### Server
 
-`@intent/server` may depend on:
+`@intent-framework/server` may depend on:
 
 ```txt
-@intent/core
+@intent-framework/core
 ```
 
 Prefer Web API concepts:

README.md

@@ -65,7 +65,7 @@ The renderer then materializes that graph.
 ## Tiny example
 
 ```ts
-import { screen, state } from "@intent/core"
+import { screen, state } from "@intent-framework/core"
 
 export const InviteScreen = screen("Invite", $ => {
   const email = $.state.text("email")
@@ -159,11 +159,11 @@ This repository currently contains:
 
 | Package           | Purpose                                 |
 | ----------------- | --------------------------------------- |
-| `@intent/core`    | Platformless semantic graph and runtime |
-| `@intent/dom`     | DOM materializer for screens and router |
-| `@intent/router`  | Typed route definitions and navigation  |
-| `@intent/testing` | Semantic test harness                   |
-| `@intent/server`  | Early server-side package               |
+| `@intent-framework/core`    | Platformless semantic graph and runtime |
+| `@intent-framework/dom`     | DOM materializer for screens and router |
+| `@intent-framework/router`  | Typed route definitions and navigation  |
+| `@intent-framework/testing` | Semantic test harness                   |
+| `@intent-framework/server`  | Early server-side package               |
 
 The core package must remain platformless. It should not import DOM, React, router internals, server framework code, or native APIs.
 

docs/Demo.md

@@ -144,11 +144,11 @@ Key patterns:
 See the MVP scope in `AGENTS.md`. The following are explicitly out of scope for
 the current MVP:
 
-- `@intent/devtools` — no DevTools extension or debugger UI
-- `@intent/openapi` — no OpenAPI contract generation
-- `@intent/realtime` — no WebSocket or SSE subscriptions
-- `@intent/react-native` — no native renderer
-- `@intent/compiler` — no build-time graph analysis
+- `@intent-framework/devtools` — no DevTools extension or debugger UI
+- `@intent-framework/openapi` — no OpenAPI contract generation
+- `@intent-framework/realtime` — no WebSocket or SSE subscriptions
+- `@intent-framework/react-native` — no native renderer
+- `@intent-framework/compiler` — no build-time graph analysis
 - Complex SSR, streaming hydration, or edge adapters
 - Visual editor or AI assistant
 - Design system or CSS framework integration

docs/MVP-Checkpoint.md

@@ -54,11 +54,11 @@ It now has:
 
 ## Implemented packages
 
-- `@intent/core` — semantic graph and runtime ([packages/core](../packages/core))
-- `@intent/dom` — DOM materializer ([packages/dom](../packages/dom))
-- `@intent/router` — typed route definitions ([packages/router](../packages/router))
-- `@intent/testing` — semantic test harness ([packages/testing](../packages/testing))
-- `@intent/server` — early server package ([packages/server](../packages/server))
+- `@intent-framework/core` — semantic graph and runtime ([packages/core](../packages/core))
+- `@intent-framework/dom` — DOM materializer ([packages/dom](../packages/dom))
+- `@intent-framework/router` — typed route definitions ([packages/router](../packages/router))
+- `@intent-framework/testing` — semantic test harness ([packages/testing](../packages/testing))
+- `@intent-framework/server` — early server package ([packages/server](../packages/server))
 
 ## Implemented primitives
 
@@ -83,7 +83,7 @@ Demo limitations: manual DOM side panels, `MutationObserver`-driven diagnostics
 
 - CI runs clean-dist validation on every PR and push to `main`.
 - Validation: `rm -rf packages/*/dist examples/*/dist` then `pnpm test && pnpm typecheck && pnpm build && pnpm lint`.
-- Tests assert semantic behavior via `@intent/testing` and core inspection APIs.
+- Tests assert semantic behavior via `@intent-framework/testing` and core inspection APIs.
 
 ## Architectural boundaries
 

docs/Release-Readiness.md

@@ -12,17 +12,17 @@ All five packages under `packages/*` are intended to be published:
 
 | Package | npm name | Purpose |
 |---|---|---|
-| `packages/core` | `@intent/core` | Platformless semantic graph and runtime |
-| `packages/dom` | `@intent/dom` | DOM materializer for screens and router |
-| `packages/router` | `@intent/router` | Typed route definitions and navigation |
-| `packages/testing` | `@intent/testing` | Semantic test harness |
-| `packages/server` | `@intent/server` | Early server-side package |
+| `packages/core` | `@intent-framework/core` | Platformless semantic graph and runtime |
+| `packages/dom` | `@intent-framework/dom` | DOM materializer for screens and router |
+| `packages/router` | `@intent-framework/router` | Typed route definitions and navigation |
+| `packages/testing` | `@intent-framework/testing` | Semantic test harness |
+| `packages/server` | `@intent-framework/server` | Early server-side package |
 
 Packages under `examples/` (e.g., `web-basic`) are private and must not be published.
 
 ## Package audit
 
-### `@intent/core`
+### `@intent-framework/core`
 
 | Field | Value | Status |
 |---|---|---|
@@ -40,7 +40,7 @@ Packages under `examples/` (e.g., `web-basic`) are private and must not be publi
 | Build tool | `tsdown` | Bundles ESM + `.d.ts` |
 | Test harness | `vitest` | Tests pass |
 
-### `@intent/dom`
+### `@intent-framework/dom`
 
 | Field | Value | Status |
 |---|---|---|
@@ -53,10 +53,10 @@ Packages under `examples/` (e.g., `web-basic`) are private and must not be publi
 | `description` | Present | Added in this audit |
 | `license` | MIT field present | Root LICENSE file present |
 | `repository` | Missing | Recommended |
-| `dependencies` | `@intent/core`, `@intent/router` | Uses `workspace:*` — correct for monorepo |
+| `dependencies` | `@intent-framework/core`, `@intent-framework/router` | Uses `workspace:*` — correct for monorepo |
 | Build tool | `tsdown` | Bundles ESM + `.d.ts` |
 
-### `@intent/router`
+### `@intent-framework/router`
 
 | Field | Value | Status |
 |---|---|---|
@@ -69,10 +69,10 @@ Packages under `examples/` (e.g., `web-basic`) are private and must not be publi
 | `description` | Present | Added in this audit |
 | `license` | MIT field present | Root LICENSE file present |
 | `repository` | Missing | Recommended |
-| `dependencies` | `@intent/core` | Uses `workspace:*` |
+| `dependencies` | `@intent-framework/core` | Uses `workspace:*` |
 | Build tool | `tsdown` | Bundles ESM + `.d.ts` |
 
-### `@intent/testing`
+### `@intent-framework/testing`
 
 | Field | Value | Status |
 |---|---|---|
@@ -85,10 +85,10 @@ Packages under `examples/` (e.g., `web-basic`) are private and must not be publi
 | `description` | Present | Added in this audit |
 | `license` | MIT field present | Root LICENSE file present |
 | `repository` | Missing | Recommended |
-| `dependencies` | `@intent/core` | Uses `workspace:*` |
+| `dependencies` | `@intent-framework/core` | Uses `workspace:*` |
 | Build tool | `tsdown` | Bundles ESM + `.d.ts` |
 
-### `@intent/server`
+### `@intent-framework/server`
 
 | Field | Value | Status |
 |---|---|---|
@@ -101,27 +101,21 @@ Packages under `examples/` (e.g., `web-basic`) are private and must not be publi
 | `description` | Present | Added in this audit |
 | `license` | MIT field present | Root LICENSE file present |
 | `repository` | Missing | Recommended |
-| `dependencies` | `@intent/core` | Uses `workspace:*` |
+| `dependencies` | `@intent-framework/core` | Uses `workspace:*` |
 | Build tool | `tsdown` | Bundles ESM + `.d.ts` |
 | Note | Early stage | Server package has global registries and basic action/resource/policy types. Not yet production-ready. |
 
-## Package naming and npm scope risk
+## Package naming
 
-All five packages use the `@intent/*` npm scope.
+All five packages use the `@intent-framework/*` npm scope.
 
-**Before publishing, confirm ownership or availability of the `@intent` npm organization/scope.**
+The `intent-framework` npm organization has been created. The scope is:
 
-If `@intent` is unavailable, choose a different public scope (e.g., `@intent-framework/*`, `@intentjs/*`, or another unique name) before first release. Changing the scope after publishing is disruptive.
-
-Current package names:
-
-- `@intent/core`
-- `@intent/dom`
-- `@intent/router`
-- `@intent/testing`
-- `@intent/server`
-
-These names are descriptive and low-risk if the `@intent` scope is available. Scope availability has not been verified.
+- `@intent-framework/core`
+- `@intent-framework/dom`
+- `@intent-framework/router`
+- `@intent-framework/testing`
+- `@intent-framework/server`
 
 ## Build outputs
 
@@ -157,27 +151,27 @@ All packages expose a single entry point `"."` with three conditions:
 }
 ```
 
-This is correct for ESM-only packages. No package currently exposes sub-path exports (e.g., `@intent/core/internal`), which is fine for alpha.
+This is correct for ESM-only packages. No package currently exposes sub-path exports (e.g., `@intent-framework/core/internal`), which is fine for alpha.
 
 ## Type declarations
 
 All packages produce `dist/index.d.ts` with correct type declarations.
 
-The root `tsconfig.typecheck.json` maps `@intent/*` workspace packages to their source directories for type-checking without reading stale `dist/` output.
+The root `tsconfig.typecheck.json` maps `@intent-framework/*` workspace packages to their source directories for type-checking without reading stale `dist/` output.
 
-Package-level `tsconfig.json` files use `composite: true` (except `@intent/server`, which lacks it) and extend the root config.
+Package-level `tsconfig.json` files use `composite: true` (except `@intent-framework/server`, which lacks it) and extend the root config.
 
 ## Files included in npm packages
 
 The `files` field in every package is `["dist"]`. Based on `npm pack --dry-run` output:
 
 | Package | Files in tarball | Size |
 |---|---|---|
-| `@intent/core` | 13 `dist/*` files + `package.json` (14 total) | 38.5 kB unpacked |
-| `@intent/dom` | 4 `dist/*` files + `package.json` (4 total) | 10.9 kB unpacked |
-| `@intent/router` | 3 `dist/*` files + `package.json` (4 total) | 6.5 kB unpacked |
-| `@intent/testing` | 2 `dist/*` files + `package.json` (3 total) | 4.5 kB unpacked |
-| `@intent/server` | 2 `dist/*` files + `package.json` (3 total) | 4.2 kB unpacked |
+| `@intent-framework/core` | 13 `dist/*` files + `package.json` (14 total) | 38.5 kB unpacked |
+| `@intent-framework/dom` | 4 `dist/*` files + `package.json` (4 total) | 10.9 kB unpacked |
+| `@intent-framework/router` | 3 `dist/*` files + `package.json` (4 total) | 6.5 kB unpacked |
+| `@intent-framework/testing` | 2 `dist/*` files + `package.json` (3 total) | 4.5 kB unpacked |
+| `@intent-framework/server` | 2 `dist/*` files + `package.json` (3 total) | 4.2 kB unpacked |
 
 No unnecessary files (source maps, config files, tests, node_modules) leak into the tarball. The `files` policy is correct.
 
@@ -227,7 +221,7 @@ Do not manually create GitHub Releases.
 
 ## First alpha release checklist
 
-- [ ] Confirm npm scope/package names (verify `@intent` org ownership)
+- [x] npm scope is `@intent-framework/*` — `intent-framework` org created, packages renamed
 - [ ] Reconfirm MIT is the intended public license before publishing
 - [ ] Confirm package metadata (`repository` field in all packages)
 - [ ] Confirm package exports (all point to correct `dist/` paths — already correct)
@@ -245,18 +239,17 @@ Do not manually create GitHub Releases.
 Before first alpha release, the following must be resolved:
 
 1. **Missing `repository` fields** — Recommended for npm listing and source links.
-2. **`@intent` npm scope availability** — Must be verified. If unavailable, a fallback scope must be chosen before first release.
-3. **No release workflow** — Changesets and a GitHub Action must be added before publishing.
-4. **Server package is very early** — `@intent/server` has global registries and minimal API surface. Consider whether to publish it or mark it as private until more mature.
-5. **Version is `0.1.0` across all packages** — Consistent, but no pre-release tag (e.g., `0.1.0-alpha.0`) for the first publish.
+2. **No release workflow** — Changesets and a GitHub Action must be added before publishing.
+3. **Server package is very early** — `@intent-framework/server` has global registries and minimal API surface. Consider whether to publish it or mark it as private until more mature.
+4. **Version is `0.1.0` across all packages** — Consistent, but no pre-release tag (e.g., `0.1.0-alpha.0`) for the first publish.
 
 ## Do not do yet
 
 - Do not publish any package to npm.
 - Do not create a GitHub Release.
 - Do not add Changesets yet — wait until the audit blockers are resolved.
 - Do not add a release GitHub Action yet.
-- Do not change package names, versions, or public APIs.
+- Do not change versions or public APIs.
 - Do not add new dependencies unless required for a specific task.
 
 ## Pack check command

examples/web-basic/package.json

@@ -11,9 +11,9 @@
     "lint": "tsc --noEmit"
   },
   "dependencies": {
-    "@intent/core": "workspace:*",
-    "@intent/dom": "workspace:*",
-    "@intent/router": "workspace:*"
+    "@intent-framework/core": "workspace:*",
+    "@intent-framework/dom": "workspace:*",
+    "@intent-framework/router": "workspace:*"
   },
   "devDependencies": {
     "typescript": "^5.7.0",

examples/web-basic/src/demo-panels.ts

@@ -1,4 +1,4 @@
-import { inspectScreen, type ScreenDefinition } from "@intent/core"
+import { inspectScreen, type ScreenDefinition } from "@intent-framework/core"
 import type { AppServices } from "./types.js"
 import { teams, teamVersions } from "./data.js"
 

examples/web-basic/src/main.ts

@@ -1,4 +1,4 @@
-import { renderRouter } from "@intent/dom"
+import { renderRouter } from "@intent-framework/dom"
 import { router } from "./router.js"
 import { NotFoundScreen } from "./screens.js"
 import { updateTeamInfo, updateDiagnostics } from "./demo-panels.js"

examples/web-basic/src/router.ts

@@ -1,4 +1,4 @@
-import { createRouter } from "@intent/router"
+import { createRouter } from "@intent-framework/router"
 import { appPaths, type AppServices } from "./types.js"
 import { HomeScreen, TeamDetailScreen, InviteScreen } from "./screens.js"
 

examples/web-basic/src/screens.ts

@@ -1,4 +1,4 @@
-import { screen } from "@intent/core"
+import { screen } from "@intent-framework/core"
 import type { AppServices } from "./types.js"
 import { loadTeam, inviteMember } from "./data.js"