primitive-admin 1.1.0-alpha.50 → 1.1.0-alpha.51

package/assets/skill/skills/primitive-platform/SKILL.md

@@ -7,7 +7,9 @@ description: >
   users/groups). Also trigger whenever about to run any `primitive` CLI command (e.g., primitive sync, primitive integrations, primitive apps, primitive env) to ensure Step 0 CLI verification is performed first. After writing or modifying code that touches Primitive
   APIs, this skill cross-references the implementation against official guides and automatically
   corrects common mistakes. Use this skill even if the user doesn't explicitly ask for it —
-  any Primitive-related code should be validated against current best practices.
+  any Primitive-related code should be validated against current best practices. Also use it
+  when something looks like a platform bug or missing platform capability, to decide whether
+  (and how) to file a platform issue.
 allowed-tools: Bash, Read, Edit, Write, Glob, Grep, Agent
 ---
 
@@ -279,3 +281,91 @@ For any question about Primitive platform capabilities:
 3. **Answer from the guide content** — don't guess or make up APIs
 4. **Include working code examples** from the guide
 5. **Point the user to the guide** for further reading: "You can see more examples by running `primitive guides get <topic>`"
+
+## Filing Platform Issues
+
+Sometimes the problem is in the platform itself — a bug in js-bao, the client library,
+the CLI, or a capability the platform doesn't have — rather than in the user's app.
+Platform work is tracked as GitHub issues on `Primitive-Labs/js-bao-wss`.
+
+**Gate: only suggest filing an issue if the signed-in GitHub user is a member of the
+Primitive-Labs org.** Check silently before ever raising the option:
+
+```bash
+gh api user/memberships/orgs/Primitive-Labs --jq .state 2>/dev/null
+```
+
+If this doesn't print `active` (not a member, or `gh` is missing or unauthenticated),
+don't mention filing an issue at all — help the user work around the problem instead.
+
+### Issue hygiene
+
+Issues are read by an agent pipeline and by maintainers who have none of your session's
+context. The description is all they get, and investigating is the assignee's job —
+yours is to state the problem clearly.
+
+- **Brevity and clarity win over verbosity.** Keep the prose to 1000 characters or
+  less. Fenced code blocks (repro commands, config, verbatim error output) don't count
+  toward the cap — precision there is what makes an issue reproducible. If the prose
+  doesn't fit, you're including solution detail or context the assignee can rediscover.
+- **Self-contained.** Assume the reader knows nothing about the user's app and has no
+  internal knowledge of the platform. Reference related issues by number, but inline
+  whatever context is needed to read the issue standalone.
+- **Describe the problem, not the solution.** Don't prescribe the fix or assume a
+  particular implementation.
+- **Don't relitigate decisions rejected in earlier issues** — carry forward the
+  discovered tradeoffs, stated neutrally.
+
+### Bugs (an existing platform feature not working as designed)
+
+Body template — fill each section with as much precision as possible, so the issue is
+easy to reproduce on the first try:
+
+```
+## Repro steps
+<numbered, precise steps: exact API calls, config, versions>
+
+## Observed behavior
+<what actually happens, with verbatim error text>
+
+## Expected behavior
+<what should happen instead>
+```
+
+Labels: `type:bug` + `stage:ready-to-implement` when the repro is precise and clearly
+reproducible; otherwise `type:bug` + `stage:design`.
+
+### Features / enhancements / platform extensions
+
+```
+## Problem
+<the application-level problem being solved>
+
+## What I tried
+<existing platform features attempted, and why each falls short — omit if none apply>
+
+## Ideas
+<high-level directions as bullets, not specs>
+```
+
+Labels: `type:feature` + `stage:design`.
+
+### Filing
+
+Use only `type:bug` or `type:feature` (e.g. file performance problems as `type:bug`
+with measurements in the repro steps). Search open issues for duplicates first:
+
+```bash
+gh issue list --repo Primitive-Labs/js-bao-wss --search "<keywords>" --state open \
+  --json number,title
+```
+
+Then create the issue with labels only — **no assignee** (triage assigns sponsors;
+unassigned is the correct starting state) and no priority labels:
+
+```bash
+gh issue create --repo Primitive-Labs/js-bao-wss \
+  --title "<one-line symptom or need>" \
+  --label "type:bug,stage:design" \
+  --body "<template body>"
+```

package/dist/src/commands/sync.d.ts

@@ -246,6 +246,7 @@ export declare function rewriteWorkflowSchemasToNative(rawToml: string, workflow
     changed: boolean;
 };
 export declare function serializeWorkflow(workflow: any, draft: any, configs: any[], logger?: (message: string) => void): string;
+export declare function serializeRuleSet(ruleSet: any): string;
 export declare function serializeGroupTypeConfig(config: any, ruleSetIdToName: Map<string, string>): string;
 /**
  * Issue #1567 — the TOML-owned scalar fields of a database-type config.
@@ -291,6 +292,7 @@ export declare function parseDatabaseTypeToml(tomlData: any): {
     operations: any[];
     subscriptions: any[];
 };
+export declare function parseRuleSetToml(tomlData: any): any;
 export declare function parseGroupTypeConfigToml(tomlData: any): any;
 export declare function parseCollectionTypeConfigToml(tomlData: any): any;
 export declare function hashLocalRuleSetForDiff(parsedToml: any): string;

package/dist/src/commands/sync.js

@@ -972,7 +972,7 @@ function serializeEmailTemplate(template) {
     }
     return stringifyConfigToml(data);
 }
-function serializeRuleSet(ruleSet) {
+export function serializeRuleSet(ruleSet) {
     const data = {
         ruleSet: {
             name: ruleSet.name,
@@ -1181,7 +1181,7 @@ export function parseDatabaseTypeToml(tomlData) {
     const subscriptions = (tomlData.subscriptions || []).map((sub) => normalizeSubscriptionFromToml(sub));
     return { typeConfig, operations, subscriptions };
 }
-function parseRuleSetToml(tomlData) {
+export function parseRuleSetToml(tomlData) {
     const ruleSetSection = tomlData.ruleSet || {};
     return {
         name: ruleSetSection.name,