@vifu/vf 0.1.0-alpha.14-darwin-arm64

package/README.md

@@ -0,0 +1,173 @@
+# VifuHub CLI
+
+`vf` is the command-line tool for building, checking, and publishing playable
+AI-native game releases to VifuHub.
+
+```bash
+vf manifest check
+vf build
+vf deploy
+```
+
+When run from a game directory, `vf deploy` resolves the local project,
+validates `manifest.json`, builds the game, checks the Agent Runtime artifact,
+uploads only when the artifact is valid, and prints the playable URL.
+
+## Install
+
+```bash
+curl -fsSL https://vifu.ai/cli | bash
+vf --help
+```
+
+For repeated use inside one project:
+
+```bash
+npm install --save-dev @vifu/vf
+npx vf --help
+```
+
+## Agent Workflows
+
+Install the VifuHub CLI skill separately from
+[github.com/vifudotdev/skills](https://github.com/vifudotdev/skills):
+
+```bash
+npx skills add vifudotdev/skills --skill "vifuhub-cli"
+```
+
+Then a coding agent can start from the current directory:
+
+```text
+Use the VifuHub CLI skill. Deploy this game directory and report the Playable URL.
+```
+
+The skill tells agents to check `vf --help`, then use the one-step deploy path:
+
+```bash
+vf deploy --yes
+```
+
+`vf deploy --yes` creates missing setup from detected defaults, builds, checks
+the output, uploads the valid artifact, and prints `Playable URL:` when sharing
+succeeds. If authentication is missing, run:
+
+```bash
+vf login
+```
+
+Create a new project:
+
+```bash
+npm create @vifu/vifu my-game -- --template vanilla --no-interactive
+cd my-game
+vf deploy --yes
+```
+
+Deploy an existing project:
+
+```bash
+cd path/to/game
+vf deploy --yes
+```
+
+You can also pass the project path explicitly:
+
+```bash
+vf deploy ./path/to/game
+```
+
+## Manifest
+
+Every deployable game has a public V1 `manifest.json`:
+
+```json
+{
+  "name": "my-ai-game"
+}
+```
+
+VifuHub fills deployable defaults and infers common build settings from the
+project. Add fields only when you need to override detection or disable an
+Agent Runtime feature. Do not put internal runtime keys such as `runtime`,
+`services`, `devices`, `resources`, `permissions`, `capabilities`, `browser`,
+or `security` in public game manifests.
+
+Useful commands:
+
+```bash
+vf manifest check
+vf manifest check --dir ./path/to/game
+vf manifest explain
+vf manifest explain --dir ./path/to/game --debug
+```
+
+`manifest explain --debug` is for Agent Runtime development. It shows the
+compiled internal policy that the runtime will enforce.
+
+## Release Policy
+
+`vf deploy` and `vf publish` treat the built output as the reviewed Agent
+Runtime artifact. The CLI does not rewrite the game, download CDN scripts, or
+create a deploy lockfile.
+
+Allowed:
+
+- bundled game JavaScript
+- local build output from Vite, Angular, Phaser, Three.js, Pixi, plain HTML, or
+  another web build tool
+- approved external static CSS, fonts, images, and media
+- AI/backend access through `@vifu/hub` or `window.Vifu`
+
+Blocked:
+
+- remote `<script src="https://...">`
+- remote JavaScript `import("https://...")`
+- remote workers or `importScripts(...)`
+- remote `.js`, `.mjs`, or `.wasm` URLs inside built files
+- direct calls to external AI/backend APIs from game JavaScript
+
+If deploy fails, read the file, line, rule, URL, and fix shown by the CLI. The
+most common cause is an optional local or third-party provider being statically
+imported into a production browser bundle.
+
+The canonical policy is [.spec/runtime-artifact-policy.md](../../.spec/runtime-artifact-policy.md).
+
+## SDK Integration
+
+Games should call Agent Runtime capabilities through the VifuHub SDK:
+
+```js
+const result = await Vifu.ai.generateText({
+  model: "quality",
+  messages: [{ role: "user", content: "Describe the next room." }]
+});
+
+await Vifu.gameState.save({ reason: "checkpoint" });
+```
+
+The SDK keeps runtime transport, host authentication, model routing, quota,
+and backend URLs out of game code. See
+[packages/sdk/README.md](../../packages/sdk/README.md).
+
+## Existing Games
+
+To adapt an existing browser game:
+
+1. Add `manifest.json`.
+2. Start with only `name`; let VifuHub infer common entry and build settings.
+3. Build a static directory with `index.html`.
+4. Replace direct AI/backend calls with the VifuHub SDK.
+5. Remove unused remote/local AI providers from the published build.
+6. Run `vf deploy`.
+
+Extra source workflows live under explicit commands:
+
+```bash
+vf remix my-remix --from ./existing-game
+vf import anki jlpt-review --apkg ./deck.apkg
+vf import podcast listening-game --feed-url https://example.com/feed.xml
+```
+
+`vf create` and `vf new` are intentionally not exposed. Use
+`npm create @vifu/vifu` for new template projects.

package/package.json

@@ -0,0 +1,23 @@
+{
+  "name": "@vifu/vf",
+  "version": "0.1.0-alpha.14-darwin-arm64",
+  "description": "Native VifuHub CLI binary for darwin-arm64.",
+  "files": [
+    "bin",
+    "README.md"
+  ],
+  "os": [
+    "darwin"
+  ],
+  "cpu": [
+    "arm64"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/chenyanming/nekodoku.git",
+    "directory": "Consenger/apps/cli"
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}