@nseng-ai/ns 0.1.0 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -3,3 +3,23 @@
3
3
  Checkout-free npm package for the `ns` CLI.
4
4
 
5
5
  The published package bin points at prebuilt JavaScript (`bin/ns.js`) assembled by the package preparation step. Developer source-checkout shims remain separate from this npm package boundary.
6
+
7
+ The package also owns the public kernel subpaths for checkout-free consumers, for example `@nseng-ai/ns/kernel/sdk` and `@nseng-ai/ns/kernel/*`. The standalone workspace `@nseng-ai/kernel` package remains private and is folded into these `@nseng-ai/ns` subpaths at package-preparation time.
8
+
9
+ ## Release preparation for `0.1.1`
10
+
11
+ `@nseng-ai/ns@0.1.1` is the publishable patch target for the checkout-free CLI host. Local release qualification should run:
12
+
13
+ ```sh
14
+ pnpm --dir ts --filter @nseng-ai/ns run publish:dry-run
15
+ pnpm --dir ts --filter @nseng-ai/ns run pack:local
16
+ pnpm --dir ts --filter @nseng-ai/ns run smoke:checkout-free
17
+ ```
18
+
19
+ The generated `dist/publish/package.json` must keep `bin.ns` at `bin/ns.js`, omit source package scripts such as the raw-root `prepublishOnly` guard, include `publishConfig.access = "public"`, and expose `@nseng-ai/ns/kernel/*` subpaths.
20
+
21
+ Actual publication is a separate authorized step; do not publish as part of local qualification. After an authorized publish, verify the registry metadata with:
22
+
23
+ ```sh
24
+ npm view @nseng-ai/ns@0.1.1 name version bin dist.tarball time --json
25
+ ```