@duypham93/openkit 0.2.0 → 0.2.1

package/.opencode/README.md

@@ -30,7 +30,7 @@ What this directory is not:
 
 When the global OpenKit install exists elsewhere, the intended product path is:
 
-- `npm install -g openkit`
+- `npm install -g @duypham93/openkit`
 - `openkit doctor`
 - `openkit run`
 - `openkit upgrade`

package/AGENTS.md

@@ -40,7 +40,7 @@ Current repository facts:
 - The current workflow contract is the hard-split design described in `context/core/workflow.md`
 - `context/core/workflow.md` is the canonical workflow-semantics document for lane behavior, stages, escalation, approvals, and quick-lane artifact expectations
 - Historical planning and example docs have been intentionally pruned from the working tree; prefer current runtime docs and git history when older rationale is needed
-- `npm install -g openkit`, `openkit run`, `openkit doctor`, `openkit upgrade`, and `openkit uninstall` now define the preferred operator path for the global OpenKit kit
+- `npm install -g @duypham93/openkit`, `openkit run`, `openkit doctor`, `openkit upgrade`, and `openkit uninstall` now define the preferred operator path for the global OpenKit kit
 - `.opencode/opencode.json` is present as the runtime manifest for this kit
 - `.opencode/workflow-state.json` is present as the active external compatibility mirror for the active work item
 - `.opencode/work-items/` is present as the internal per-item workflow backing store for managed runtime state

package/README.md

@@ -28,7 +28,7 @@ This repository currently contains two active surface types:
 
 1. **Global managed kit path**
    - the `openkit` CLI now installs the kit into the OpenCode home directory
-   - install the CLI with `npm install -g openkit`, then use `openkit run` and `openkit doctor` as the intended operator path
+   - install the CLI with `npm install -g @duypham93/openkit`, then use `openkit run` and `openkit doctor` as the intended operator path
    - global workspace state is created per project under the OpenCode home directory instead of copying the kit into each repository
 
 2. **Checked-in authoring and compatibility runtime**
@@ -79,7 +79,7 @@ The preferred product path is now the globally installed OpenKit kit. This repos
 
 Preferred global path:
 
-1. Run `npm install -g openkit` to install the CLI once on the machine.
+1. Run `npm install -g @duypham93/openkit` to install the CLI once on the machine.
 2. Run `openkit run <args>` to launch `opencode --profile openkit`; on first run, OpenKit materializes the global kit into the OpenCode home directory automatically.
 3. Run `openkit doctor` to confirm the global install and current workspace are healthy.
 4. Run `openkit upgrade` to refresh the installed global kit when a newer package version is available.
@@ -114,7 +114,7 @@ Install-direction guardrails:
 
 Repository-internal vs global-kit summary:
 
-- Global-kit user path: `npm install -g openkit`, `openkit run`, `openkit doctor`, `openkit upgrade`, and `openkit uninstall`
+- Global-kit user path: `npm install -g @duypham93/openkit`, `openkit run`, `openkit doctor`, `openkit upgrade`, and `openkit uninstall`
 - Global kit lives under the OpenCode home directory, not inside each project
 - Repository-internal authoring surface remains: `.opencode/opencode.json`, workflow-state files, the workflow-state CLI, hooks, agents, skills, commands, context, and maintained docs
 - The checked-in runtime remains useful for maintainers and compatibility testing even though end-user installation is now global-first
@@ -282,7 +282,7 @@ The command surface above is the current live interface. The live contract keeps
 
 For normal day-to-day use:
 
-- prefer `npm install -g openkit`, then `openkit run`, `openkit doctor`, `openkit upgrade`, and `openkit uninstall`
+- prefer `npm install -g @duypham93/openkit`, then `openkit run`, `openkit doctor`, `openkit upgrade`, and `openkit uninstall`
 - use the lower-level checked-in runtime path below when you are maintaining or validating this repository itself
 
 1. Run `node .opencode/workflow-state.js status` to see whether work is already in progress.

package/context/core/project-config.md

@@ -12,7 +12,7 @@ For the canonical workflow contract, including lane semantics, stage order, esca
 - There is no single canonical package manager or language toolchain for future applications yet.
 - OpenKit uses the mode-aware workflow documented in `context/core/workflow.md`; keep tooling and command guidance here aligned with that live contract instead of re-stating lane policy in full.
 - The active compatibility mirror uses a mode-aware schema and `.opencode/workflow-state.js` supports that workflow model.
-- The preferred operator install path is now global: `npm install -g openkit`, then `openkit run` and `openkit doctor`.
+- The preferred operator install path is now global: `npm install -g @duypham93/openkit`, then `openkit run` and `openkit doctor`.
 - The checked-in repository-local runtime still exists as the authoring and compatibility surface under `.opencode/`.
 - `registry.json` and `.opencode/install-manifest.json` are additive local metadata surfaces; they do not imply destructive install or plugin-only packaging.
 - Repository-internal runtime surfaces still include workflow state, workflow-state CLI, hooks, agents, skills, commands, context, and maintained docs.
@@ -37,7 +37,7 @@ For the canonical workflow contract, including lane semantics, stage order, esca
 
 These are repository workflow commands, not application build/lint/test commands:
 
-- `npm install -g openkit`
+- `npm install -g @duypham93/openkit`
 - `openkit install-global`
 - `openkit doctor`
 - `openkit run [args]`
@@ -78,7 +78,7 @@ These are repository workflow commands, not application build/lint/test commands
 Current workflow-state behavior:
 
 - The CLI understands the current mode-aware workflow model.
-- `npm install -g openkit` installs the OpenKit CLI globally.
+- `npm install -g @duypham93/openkit` installs the OpenKit CLI globally.
 - `openkit run` materializes the globally managed kit into the OpenCode home directory on first use when needed.
 - `openkit doctor` checks the global install and the current workspace bootstrap.
 - `openkit install-global` remains available as a manual or compatibility setup path.

package/docs/maintainer/README.md

@@ -38,7 +38,7 @@ Use it to find canonical repository docs and upkeep surfaces quickly. Do not tre
 
 ## Global Install Notes
 
-- The preferred end-user onboarding path is `npm install -g openkit` followed by `openkit run`.
+- The preferred end-user onboarding path is `npm install -g @duypham93/openkit` followed by `openkit run`.
 - The first `openkit run` materializes the managed kit into the OpenCode home directory automatically.
 - `openkit doctor` is the read-only check for the global install and workspace bootstrap state.
 - `openkit install-global`, `openkit install`, and `openkit init` remain available as manual or compatibility commands.

package/docs/operations/README.md

@@ -27,7 +27,7 @@ Prefer the global install path first for everyday use. Use the checked-in reposi
 
 When OpenKit is installed globally, start with:
 
-- `npm install -g openkit`
+- `npm install -g @duypham93/openkit`
 - `openkit run`
 - `openkit doctor` for global install readiness, drift, and missing-prerequisite checks
 - `openkit run <args>` for the supported global launcher path and first-time setup

package/docs/operations/internal-records/2026-03-24-release-checklist.md

@@ -1,18 +1,18 @@
-# OpenKit 0.2.0 Release Checklist
+# OpenKit 0.2.1 Release Checklist
 
 Date: 2026-03-24
 
 ## Scope
 
-- simplified onboarding with `npm install -g openkit` followed by `openkit run`
+- simplified onboarding with `npm install -g @duypham93/openkit` followed by `openkit run`
 - automatic first-run global kit setup when the install is missing
 - doctor guidance with `Next:` and `Recommended command:` output
 - manual and compatibility retention for `openkit install-global`, `openkit install`, and `openkit init`
 
 ## Pre-Publish
 
-- confirm `package.json` version is `0.2.0`
-- confirm docs describe `npm install -g openkit` and `openkit run` as the preferred path
+- confirm `package.json` version is `0.2.1`
+- confirm docs describe `npm install -g @duypham93/openkit` and `openkit run` as the preferred path
 - confirm release note draft is up to date in `docs/operations/internal-records/2026-03-24-simplified-install-ux.md`
 - run:
 
@@ -26,7 +26,7 @@ node --test tests/cli/openkit-cli.test.js tests/global/*.test.js tests/runtime/*
 npm pack
 ```
 
-- verify the tarball name is `openkit-0.2.0.tgz`
+- verify the tarball name is `duypham93-openkit-0.2.1.tgz`
 
 ## Local Smoke Test
 
@@ -50,13 +50,13 @@ npm publish
 - verify the published version:
 
 ```bash
-npm view openkit version
+npm view @duypham93/openkit version
 ```
 
 - install globally on a clean machine or temporary prefix:
 
 ```bash
-npm install -g openkit
+npm install -g @duypham93/openkit
 ```
 
 - verify:
@@ -75,5 +75,5 @@ openkit doctor
 ```text
 simplify global OpenKit onboarding
 
-Make `openkit run` perform first-time global setup automatically so users can start with `npm install -g openkit` and launch immediately. Update doctor guidance, command help, docs, and tests to support the new onboarding flow while keeping manual install commands for compatibility.
+Make `openkit run` perform first-time global setup automatically so users can start with `npm install -g @duypham93/openkit` and launch immediately. Update doctor guidance, command help, docs, and tests to support the new onboarding flow while keeping manual install commands for compatibility.
 ```

package/docs/operations/internal-records/2026-03-24-simplified-install-ux.md

@@ -4,7 +4,7 @@ Date: 2026-03-24
 
 ## Change Summary
 
-- the preferred onboarding flow is now `npm install -g openkit` followed by `openkit run`
+- the preferred onboarding flow is now `npm install -g @duypham93/openkit` followed by `openkit run`
 - `openkit run` performs first-time global kit setup automatically when the install is missing
 - `openkit doctor` now reports next-step guidance and recommended commands
 - `openkit install-global`, `openkit install`, and `openkit init` remain available as manual or compatibility commands
@@ -20,7 +20,7 @@ Date: 2026-03-24
 - new-user quickstart:
 
 ```bash
-npm install -g openkit
+npm install -g @duypham93/openkit
 openkit run
 openkit doctor
 ```
@@ -30,7 +30,7 @@ openkit doctor
 
 ## Release Notes Draft
 
-- Simplified onboarding so users can install the CLI with `npm install -g openkit` and start with `openkit run`
+- Simplified onboarding so users can install the CLI with `npm install -g @duypham93/openkit` and start with `openkit run`
 - Added automatic first-run global kit setup when the managed install is missing
 - Added doctor guidance with `Next:` and `Recommended command:` output for missing, invalid, healthy, and workspace-issue states
 - Kept `openkit install-global`, `openkit install`, and `openkit init` for manual and compatibility workflows

package/docs/operations/runbooks/openkit-daily-usage.md

@@ -16,7 +16,7 @@ Use this runbook when you want the practical step-by-step path for working with
 For normal day-to-day use on a machine with OpenKit installed globally:
 
 ```bash
-npm install -g openkit
+npm install -g @duypham93/openkit
 openkit run
 openkit doctor
 ```
@@ -267,7 +267,7 @@ Use the output to confirm the active stage, linked artifacts, and any task-board
 The preferred top-level path is now:
 
 ```bash
-npm install -g openkit
+npm install -g @duypham93/openkit
 openkit run <args>
 openkit doctor
 openkit upgrade

package/docs/operations/runbooks/workflow-state-smoke-tests.md

@@ -32,7 +32,7 @@ These checks validate OpenKit's supported wrapper operator path plus the workflo
 
 When you are validating operator-facing behavior, treat this order as primary:
 
-1. `npm install -g openkit`
+1. `npm install -g @duypham93/openkit`
 2. `openkit run`
 3. `openkit doctor`
 4. `node .opencode/workflow-state.js ...` only when you need raw repository/runtime inspection
@@ -126,7 +126,7 @@ Run the manual checks below only in a throwaway repo or temporary project copy u
 On a fresh machine or temporary OpenCode home:
 
 ```bash
-npm install -g openkit
+npm install -g @duypham93/openkit
 openkit run
 openkit doctor
 ```

package/docs/operator/README.md

@@ -16,7 +16,7 @@ Use it to find the right live docs quickly. Do not treat it as a canonical repla
 
 - Read `README.md` for the top-level product and runtime boundary summary
 - Read `docs/operations/runbooks/openkit-daily-usage.md` for the detailed day-to-day usage path in this repository
-- Install the CLI with `npm install -g openkit`, then run `openkit run` for first-time setup and `openkit doctor` to verify readiness
+- Install the CLI with `npm install -g @duypham93/openkit`, then run `openkit run` for first-time setup and `openkit doctor` to verify readiness
 - Use `/task` unless you already know the work must start in `Quick Task`, `Migration`, or `Full Delivery`
 - Use `context/navigation.md` when you need to locate deeper workflow or standards references
 
@@ -36,7 +36,7 @@ Use it to find the right live docs quickly. Do not treat it as a canonical repla
 - Slash commands: `/task`, `/quick-task`, `/migrate`, `/delivery`, `/brainstorm`, `/write-plan`, `/execute-plan`
 - Global diagnostics: `openkit doctor`
 - Global launcher: `openkit run`
-- Global lifecycle: `npm install -g openkit`, `openkit upgrade`, `openkit uninstall`
+- Global lifecycle: `npm install -g @duypham93/openkit`, `openkit upgrade`, `openkit uninstall`
 - Runtime inspection: `node .opencode/workflow-state.js status`
 - Compatibility diagnostics: `node .opencode/workflow-state.js doctor`
 - Current state view: `node .opencode/workflow-state.js show`

package/docs/plans/2026-03-23-openkit-global-install-runtime.md

@@ -32,8 +32,8 @@ approval_gate: tech_lead_to_fullstack
 ## Target UX
 
 - Fresh machine install:
-  - `npx openkit@latest install-global`
-  - `npx openkit@latest doctor`
+  - `npx @duypham93/openkit@latest install-global`
+  - `npx @duypham93/openkit@latest doctor`
 - Day-to-day usage in any repo:
   - `opencode --profile openkit`
 - Existing repo should not need checked-in `agents/`, `skills/`, `commands/`, or `.opencode/` surfaces just to use the kit.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@duypham93/openkit",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "type": "module",
   "files": [
     ".opencode/",

package/src/cli/commands/help.js

@@ -3,7 +3,7 @@ function topLevelHelp() {
     'Usage: openkit <command> [options]',
     '',
     'Quickstart:',
-    '  npm install -g openkit',
+    '  npm install -g @duypham93/openkit',
     '  openkit run',
     '',
     'Commands:',

package/tests/cli/openkit-cli.test.js

@@ -37,7 +37,7 @@ test('openkit --help shows global-install oriented help', () => {
   const result = runCli(['--help']);
 
   assert.equal(result.status, 0);
-  assert.match(result.stdout, /npm install -g openkit/);
+  assert.match(result.stdout, /npm install -g @duypham93\/openkit/);
   assert.match(result.stdout, /perform first-time setup if needed/);
   assert.match(result.stdout, /install-global/);
   assert.match(result.stdout, /upgrade/);