@playdrop/playdrop-cli 0.5.1 → 0.5.3

package/node_modules/@playdrop/config/dist/src/creator-faq.js

@@ -0,0 +1,141 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.CREATOR_FAQ_SECTIONS = void 0;
+exports.CREATOR_FAQ_SECTIONS = [
+    {
+        id: 'platform',
+        title: 'Platform model',
+        description: 'What Playdrop is for creators and what kind of work belongs here.',
+        items: [
+            {
+                question: 'What is PlayDrop for creators?',
+                answer: 'PlayDrop is both a catalogue platform and a runtime platform. You can publish apps, assets, and packs into the catalogue, then use Playdrop runtime services such as identity, saves, multiplayer, monetization, AI generation, and player meta inside hosted apps.',
+                links: [
+                    { href: '/getting-started', label: 'Getting Started' },
+                    { href: '/docs/catalogue', label: 'Catalogue docs' },
+                    { href: '/docs/runtime', label: 'Runtime docs' },
+                ],
+            },
+            {
+                question: 'What can I publish?',
+                answer: 'Creators can publish apps, reusable assets, and asset packs. The catalogue model is versioned, supports remixing, and connects publishing with discovery and social signals.',
+                links: [
+                    { href: '/docs/catalogue#apps-assets-and-packs', label: 'Apps, assets, and packs' },
+                    { href: '/docs/publishing#catalogue-json', label: 'Catalogue JSON' },
+                ],
+            },
+            {
+                question: 'Do I need to think about players first?',
+                answer: 'Not for onboarding. The creator workflow matters first: set up the tools, choose the right content model, run locally, validate, and publish. Player-facing launch behavior is mostly obvious once the content exists.',
+            },
+        ],
+    },
+    {
+        id: 'tooling',
+        title: 'Tooling and agents',
+        description: 'How the CLI, the public skill, and AI coding agents fit together.',
+        items: [
+            {
+                question: 'Do I need the PlayDrop skill, the CLI, or both?',
+                answer: 'Use both. The CLI performs the real workflows such as auth, create, remix, dev, validate, publish, browse, and comments. The public PlayDrop skill gives your coding agent the platform-specific workflow and vocabulary so it uses the CLI and runtime correctly.',
+                links: [
+                    { href: '/getting-started', label: 'Getting Started' },
+                    { href: '/docs/cli#install-and-auth', label: 'CLI install and auth' },
+                ],
+            },
+            {
+                question: 'How should AI agents fit into the workflow?',
+                answer: 'Let the agent do the setup and implementation work, but keep the human request small and outcome-focused. A good creator prompt tells the agent to install the PlayDrop tooling, authenticate, inspect the workspace, and then choose the correct create, remix, or publish flow.',
+                links: [
+                    { href: '/getting-started', label: 'Creator onboarding' },
+                ],
+            },
+            {
+                question: 'Can I log in without browser auth?',
+                answer: 'Yes. The CLI supports browser login by default and also supports API key login with playdrop auth login --key <api-key>. Direct username and password login is also supported when you need it.',
+                links: [
+                    { href: '/docs/cli#install-and-auth', label: 'Auth workflows' },
+                ],
+            },
+        ],
+    },
+    {
+        id: 'publishing',
+        title: 'Publishing and catalogue operations',
+        description: 'How workspace content, publishing, versioning, and catalogue discovery fit together.',
+        items: [
+            {
+                question: 'What is the relationship between my workspace and the catalogue?',
+                answer: 'Your workspace is the local source of truth while you are building. catalogue.json describes the publishable apps, assets, and packs in that workspace. Validation checks the local contract, and publish pushes the current workspace state into the PlayDrop catalogue.',
+                links: [
+                    { href: '/docs/publishing#catalogue-json', label: 'Catalogue JSON' },
+                    { href: '/docs/publishing#versioning-and-lifecycle', label: 'Versioning and lifecycle' },
+                ],
+            },
+            {
+                question: 'How do versions and remixing work?',
+                answer: 'Every catalogue object is versioned. Apps publish semantic versions, assets publish revisions, and packs publish versions. Remix flows let you scaffold local content from an exact published app, asset, or pack version instead of starting from scratch.',
+                links: [
+                    { href: '/docs/catalogue#discovery-and-social-signals', label: 'Discovery and social' },
+                    { href: '/docs/cli#create-dev-and-publish', label: 'Create, dev, and publish' },
+                ],
+            },
+            {
+                question: 'Does the platform include comments and discovery signals?',
+                answer: 'Yes. The creator platform includes browse and search surfaces plus comments, likes, saves, remixes, versions, and related catalogue metadata. Those signals help explain why catalogue quality and listing quality matter.',
+                links: [
+                    { href: '/docs/catalogue#discovery-and-social-signals', label: 'Discovery and social' },
+                ],
+            },
+        ],
+    },
+    {
+        id: 'runtime',
+        title: 'Runtime and app features',
+        description: 'What hosted apps get from PlayDrop at runtime.',
+        items: [
+            {
+                question: 'What runtime features does the SDK actually provide?',
+                answer: 'The runtime covers lifecycle, player identity, saves, room-based multiplayer, monetization, runtime asset access, AI generation jobs, shared runtime libraries, achievements, and leaderboards. Public docs now follow those surfaces directly instead of hiding them behind generic SDK language.',
+                links: [
+                    { href: '/docs/runtime', label: 'Runtime overview' },
+                    { href: '/docs/runtime#meta', label: 'Achievements and leaderboards' },
+                ],
+            },
+            {
+                question: 'How do assets, packs, and runtime asset loading relate?',
+                answer: 'Assets and packs live in the catalogue as creator content, but hosted apps can also inspect, search, load, and in some cases create or update content through the runtime asset APIs. That is why the catalogue docs and runtime docs need to be read together.',
+                links: [
+                    { href: '/docs/catalogue', label: 'Catalogue docs' },
+                    { href: '/docs/runtime#assets-at-runtime', label: 'Assets at runtime' },
+                ],
+            },
+            {
+                question: 'What does PlayDrop own versus what my game still owns?',
+                answer: 'PlayDrop owns the platform surfaces: host lifecycle, creator and player identity, storage hooks, room primitives, catalogue integration, commerce hooks, AI generation jobs, and player meta primitives. Your game still owns its core gameplay rules, content design, progression design, and any custom backend behavior that is outside the PlayDrop platform contract.',
+                links: [
+                    { href: '/docs/runtime#lifecycle', label: 'Runtime lifecycle' },
+                    { href: '/docs/runtime#multiplayer', label: 'Multiplayer' },
+                ],
+            },
+        ],
+    },
+    {
+        id: 'players',
+        title: 'Player questions',
+        description: 'Only the small set of player-facing questions that help reduce confusion for creators.',
+        items: [
+            {
+                question: 'Can players try content without setup?',
+                answer: 'Usually yes. Public catalogue content is browser-first, and creators do not need to design a separate install flow for basic launch and discovery.',
+            },
+            {
+                question: 'Does every player need a PlayDrop account before an app can run?',
+                answer: 'No. Hosted apps can choose whether auth is required, optional, or disabled. That is part of the app contract, not a universal platform rule.',
+                links: [
+                    { href: '/docs/runtime#identity', label: 'Identity and auth modes' },
+                ],
+            },
+        ],
+    },
+];

package/node_modules/@playdrop/config/dist/test/creator-docs.test.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=creator-docs.test.d.ts.map

package/node_modules/@playdrop/config/dist/test/creator-docs.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"creator-docs.test.d.ts","sourceRoot":"","sources":["../../test/creator-docs.test.ts"],"names":[],"mappings":""}

package/node_modules/@playdrop/config/dist/test/creator-docs.test.js

@@ -0,0 +1,36 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+const node_test_1 = __importDefault(require("node:test"));
+const strict_1 = __importDefault(require("node:assert/strict"));
+const index_1 = require("../src/index");
+(0, node_test_1.default)('creator getting started content is grouped into prompt options with commands', () => {
+    strict_1.default.equal(index_1.CREATOR_GETTING_STARTED_CONTENT.groups.length > 0, true);
+    for (const group of index_1.CREATOR_GETTING_STARTED_CONTENT.groups) {
+        strict_1.default.equal(group.title.trim().length > 0, true);
+        strict_1.default.equal(group.options.length > 0, true);
+        for (const option of group.options) {
+            strict_1.default.equal(option.title.trim().length > 0, true);
+            strict_1.default.equal(option.prompt.trim().length > 0, true);
+            strict_1.default.equal(option.commands.length > 0, true);
+        }
+    }
+});
+(0, node_test_1.default)('creator getting started content includes auth and publish workflows', () => {
+    const combined = JSON.stringify(index_1.CREATOR_GETTING_STARTED_CONTENT);
+    strict_1.default.match(combined, /playdrop auth login/);
+    strict_1.default.match(combined, /playdrop project publish/);
+});
+(0, node_test_1.default)('creator faq content is grouped into sections with answers', () => {
+    strict_1.default.equal(index_1.CREATOR_FAQ_SECTIONS.length > 0, true);
+    for (const section of index_1.CREATOR_FAQ_SECTIONS) {
+        strict_1.default.equal(section.title.trim().length > 0, true);
+        strict_1.default.equal(section.items.length > 0, true);
+        for (const item of section.items) {
+            strict_1.default.equal(item.question.trim().length > 0, true);
+            strict_1.default.equal(item.answer.trim().length > 0, true);
+        }
+    }
+});