@siglume/api-sdk 0.10.7 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,4 +1,4 @@
1
- # @siglume/api-sdk
1
+ # @siglume/api-sdk
2
2
 
3
3
  TypeScript runtime for building, testing, and registering Siglume developer apps.
4
4
 
@@ -67,22 +67,28 @@ siglume score . --remote
67
67
  siglume preflight . # checks blockers without creating a draft
68
68
  siglume register . # preflight + auto-register + confirm/publish
69
69
  siglume register . --draft-only # review-only draft staging
70
+ siglume companies # list company publishers available to this key
71
+ siglume register . --company company_123
70
72
  ```
71
73
 
72
74
  `siglume register` reads `tool_manual.json`, the local Git-ignored
73
- `runtime_validation.json`, and optional local Git-ignored
74
- `oauth_credentials.json`. Generated projects keep runtime validation and OAuth
75
- credential files Git-ignored because they can contain review keys and client
76
- secrets. SDK / HTTP automation can pass
75
+ `runtime_validation.json`. Generated projects keep runtime validation files
76
+ Git-ignored because they can contain review keys. SDK / HTTP automation can pass
77
77
  `source_url`, `source_context`, and `input_form_spec` directly to
78
78
  `auto-register`. The CLI runs preflight by default, then calls the same
79
79
  `auto-register` route used by SDK / automation clients and confirms publication
80
80
  unless `--draft-only` is set. Re-run the same `capability_key` to publish a
81
81
  non-material upgrade when checks pass. The server-side publish gate
82
- includes runtime checks, contract checks, seller OAuth checks, pricing / payout
82
+ includes runtime checks, contract checks, external OAuth declaration checks, pricing / payout
83
83
  rules, and a mandatory fail-closed LLM legal review for law compliance plus
84
84
  public-order / morals compliance.
85
85
 
86
+ Company-name publishing is founder-only in the Phase 2 MVP. Use
87
+ `publisher_type: "company"` with `company_id` in `app_manifest.yaml`, or pass
88
+ `--company <company_id>` to the CLI. Paid company listings require the
89
+ company's verified settlement wallet; Siglume does not fall back to the
90
+ registrant's personal payout wallet.
91
+
86
92
  Game APIs use the same publishing flow. To make a listing eligible for the
87
93
  dedicated Game API Store entry point, include explicit game-oriented
88
94
  `compatibility_tags` in the manifest, for example `["game", "unity",