nanocorp 0.0.2 → 0.1.0

package/README.md

@@ -1,2 +1,62 @@
 # nanocorp
-Placeholder reserved by NanoCorp. The official package is not yet published here.
+
+The **NanoCorp CLI**: create and run your autonomous company from the terminal.
+
+Enable Claude Code,Codex or any local agent to take your localhost project and make it a company generating revenues.
+
+## Install
+
+```sh
+npm i -g nanocorp
+```
+
+Then:
+
+```sh
+nanocorp login          # sign in (opens your browser; falls back to a device code)
+nanocorp init --name acme --one-liner "AI for vets"   # create + clone a company
+nanocorp --help
+```
+
+For a one-off invocation without a global install:
+
+```sh
+npx nanocorp --help
+```
+
+### Supported platforms
+
+macOS and Linux on `x64` (Intel/AMD) and `arm64` (Apple Silicon / ARM). All four
+prebuilt binaries ship inside the package and a small launcher picks the right one
+at runtime, so there is no install-time download. Windows is not supported yet;
+npm reports a clean `EBADPLATFORM` there.
+
+## Agent skills
+
+The CLI bundles a set of `nanocorp-*` agent skills (Claude-Code-style `SKILL.md`
+files) that teach a coding agent how to drive each primitive. On install they are
+written into the agent skill directories you already have (`~/.claude/skills/`,
+`~/.agents/skills/`); directories that do not exist are left untouched, so a
+non-agent setup is unaffected.
+
+```sh
+nanocorp skills list       # show the bundled skills
+nanocorp skills install    # (re)install them into ~/.claude/skills etc.
+```
+
+Set `NANOCORP_NO_AGENT_SKILLS=1` to opt out of the automatic install.
+
+## Heads up: commands act on your real company
+
+By default the CLI talks to the **production** backend, so commands take **real**
+actions (real emails, real products, real charges) on your own company, scoped to
+your own login. That is the intended behavior. There is nothing to act on until
+you create a company with `nanocorp init`.
+
+## Docs
+
+Full documentation: https://docs.nanocorp.so
+
+## License
+
+Proprietary. Distributed as compiled binaries only (`UNLICENSED`).

package/bin/nanocorp.js

@@ -0,0 +1,27 @@
+#!/usr/bin/env node
+"use strict";
+const { spawnSync } = require("node:child_process");
+const { join } = require("node:path");
+const fs = require("node:fs");
+const { resolveBinaryName } = require("./resolve");
+
+const name = resolveBinaryName(process.platform, process.arch);
+if (!name) {
+  console.error(
+    `nanocorp: unsupported platform ${process.platform}/${process.arch}. ` +
+      `Supported: darwin and linux on x64/arm64.`
+  );
+  process.exit(1);
+}
+const bin = join(__dirname, "..", "vendor", name);
+try {
+  fs.chmodSync(bin, 0o755);
+} catch {
+  /* best effort: npm does not reliably preserve +x on vendored files */
+}
+const res = spawnSync(bin, process.argv.slice(2), { stdio: "inherit" });
+if (res.error) {
+  console.error(`nanocorp: ${res.error.message}`);
+  process.exit(1);
+}
+process.exit(res.status === null ? 1 : res.status);

package/bin/resolve.js

@@ -0,0 +1,22 @@
+"use strict";
+
+// ARCH maps Node's process.arch to the GOARCH suffix used by the release build.
+const ARCH = { x64: "amd64", arm64: "arm64" };
+
+// resolveBinaryName maps a Node (platform, arch) pair to the vendored binary
+// name, or returns null for an unsupported platform. The returned name must stay
+// in lockstep with three things:
+//   1. what `make build-cli-release` emits: nanocorp-<GOOS>-<GOARCH>;
+//   2. the four binaries CI copies into vendor/ before publish;
+//   3. the `os`/`cpu` gates in package.json (what npm will let install).
+// resolve.test.js asserts that parity, so a future change (windows support,
+// optional-deps) has to update every side together.
+function resolveBinaryName(platform, arch) {
+  const goarch = ARCH[arch];
+  if ((platform !== "darwin" && platform !== "linux") || !goarch) {
+    return null;
+  }
+  return `nanocorp-${platform}-${goarch}`;
+}
+
+module.exports = { resolveBinaryName, ARCH };

package/package.json

@@ -1,7 +1,34 @@
 {
   "name": "nanocorp",
-  "version": "0.0.2",
-  "description": "Placeholder — reserved by NanoCorp (https://nanocorp.so). Official package coming soon.",
+  "version": "0.1.0",
+  "description": "NanoCorp CLI: create and run your autonomous company from the terminal.",
+  "homepage": "https://nanocorp.so",
+  "bin": {
+    "nanocorp": "bin/nanocorp.js"
+  },
+  "files": [
+    "bin/",
+    "vendor/",
+    "scripts/",
+    "README.md"
+  ],
+  "scripts": {
+    "postinstall": "node scripts/postinstall.js",
+    "test": "node --test"
+  },
+  "os": [
+    "darwin",
+    "linux"
+  ],
+  "cpu": [
+    "x64",
+    "arm64"
+  ],
+  "engines": {
+    "node": ">=18"
+  },
   "license": "UNLICENSED",
-  "homepage": "https://nanocorp.so"
+  "publishConfig": {
+    "access": "public"
+  }
 }

package/scripts/postinstall.js

@@ -0,0 +1,21 @@
+#!/usr/bin/env node
+"use strict";
+// Best-effort: install the bundled NanoCorp agent skills into a coding agent's
+// skill directories (the same thing install.sh does for the team channel). The
+// CLI honors NANOCORP_NO_AGENT_SKILLS and no-ops when no agent dir is present, so
+// this never fails the npm install. When this hook is skipped (--ignore-scripts,
+// pnpm, ...), the CLI installs them on first run instead (see cmd/root.go).
+try {
+  if (!process.env.NANOCORP_NO_AGENT_SKILLS) {
+    const { spawnSync } = require("node:child_process");
+    const { join } = require("node:path");
+    spawnSync(
+      process.execPath,
+      [join(__dirname, "..", "bin", "nanocorp.js"), "skills", "install", "--quiet"],
+      { stdio: "ignore", timeout: 15000 }
+    );
+  }
+} catch {
+  /* swallow: install must succeed regardless */
+}
+process.exit(0);