create-archos 0.0.0-stage → 0.1.0

package/LICENSE

@@ -0,0 +1,34 @@
+# Non-Commercial Source Available License
+
+Copyright (c) 2026 Arch Technologies Inc
+
+## Permissions
+
+You may:
+
+- Use this software for personal, non-commercial purposes
+- Modify the software for your own use
+- Distribute copies of the software to others for non-commercial use
+- Run instances of this software for yourself, your friends, or your family
+
+## Restrictions
+
+You may NOT:
+
+- Use this software for any commercial purpose without a separate written agreement
+- Host this software as a service for paying users
+- Sell access to an instance of this software
+- Integrate this software into a commercial product
+- Use this software to generate revenue in any form (including advertising, donations, or paid support)
+
+## Commercial Use
+
+If you wish to use this software commercially (including hosting as a service), please contact:
+
+hello@chuksemmanuel.com
+
+A commercial license agreement will be provided. Pricing is negotiable based on your use case.
+
+## No Warranty
+
+This software is provided "as is" without warranty of any kind.

package/README.md

@@ -1,3 +1,27 @@
-# Temporary Holding Version
+# create-archos
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Scaffold an archOS app without installing the CLI first:
+
+```bash
+npm create archos@latest my-app
+```
+
+It runs the same command as `arch init`, so everything the CLI accepts works here — including the
+templates, and arguments after `--`:
+
+```bash
+npm create archos@latest my-app -- --template sveltekit-fullstack
+```
+
+With no arguments it prompts for a name and a slug.
+
+Then:
+
+```bash
+cd my-app
+pnpm install
+arch dev
+```
+
+The CLI is [`archos`](https://www.npmjs.com/package/archos); this package exists so that
+`npm create archos` works, and it does nothing else.

package/args.js

@@ -0,0 +1,8 @@
+/**
+ * `npm create archos` resolves to this package and runs its bin, so the argv it
+ * receives has no command in it: everything the user typed is an argument to
+ * `arch init`.
+ */
+export function toInitArgs(argv) {
+  return ['init', ...argv];
+}

package/bin.js

@@ -0,0 +1,10 @@
+#!/usr/bin/env node
+import { createProgram } from 'archos';
+
+import { toInitArgs } from './args.js';
+
+// The scaffolding itself lives in the CLI, so this only has to hand it the
+// arguments. Running the program in process keeps prompts, output, and exit
+// codes exactly as `arch init` produces them.
+const program = createProgram();
+program.parse(['node', 'arch', ...toInitArgs(process.argv.slice(2))]);

package/package.json

@@ -1,6 +1,31 @@
 {
   "name": "create-archos",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
+  "version": "0.1.0",
+  "description": "Scaffold an archOS app: npm create archos@latest",
+  "license": "SEE LICENSE IN LICENSE",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/chuksemmanuel/archos.git",
+    "directory": "packages/create-archos"
+  },
+  "homepage": "https://github.com/chuksemmanuel/archos#readme",
+  "type": "module",
+  "bin": {
+    "create-archos": "./bin.js"
+  },
+  "files": [
+    "bin.js",
+    "args.js",
+    "README.md"
+  ],
+  "dependencies": {
+    "archos": "0.1.0"
+  },
+  "engines": {
+    "node": ">=20.11"
+  },
+  "scripts": {
+    "lint": "prettier --check bin.js args.js tests README.md package.json",
+    "test": "node --test tests/*.test.mjs"
+  }
 }