@stage5/lumine 0.2.91 → 0.2.94
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 +31 -0
- package/lib/admin.js +599 -83
- package/lib/api.js +58 -0
- package/lib/app-mcp/server.js +135 -23
- package/lib/assets.js +93 -2
- package/lib/cardcraft.js +141 -0
- package/lib/commands.js +17 -0
- package/lib/constants.js +6 -0
- package/lib/rewards.js +3 -1
- package/lib/util.js +28 -1
- package/package.json +1 -1
- package/sdk/BUILD_SDK_INDEX.md +35 -6
- package/sdk/LUMINE_ADMIN.md +28 -0
package/README.md
CHANGED
|
@@ -51,6 +51,16 @@ returns the confirmed canonical limits after commit. Running the command again
|
|
|
51
51
|
is a safe no-op that reports the already-active canonical limits. Omit the
|
|
52
52
|
target to use the current workspace or selected project.
|
|
53
53
|
|
|
54
|
+
Lumine file storage (uploaded assets and `Twinkle.files`) is counted per
|
|
55
|
+
creator across all their Builds. `lumine assets storage` shows your limit, usage
|
|
56
|
+
and any pending request. Past the default quota, `lumine assets request-storage
|
|
57
|
+
[--size 500MB|1GB|2GB] [--reason "<what it is for>"]` asks Mikey for more (the
|
|
58
|
+
next tier up when `--size` is omitted); nothing changes until he approves it.
|
|
59
|
+
Mikey reviews with `lumine admin storage list`, `show <user>`,
|
|
60
|
+
`approve <request-id> [--size <size>]`, `reject <request-id> [--reason <text>]`,
|
|
61
|
+
or grants directly with `lumine admin storage grant <user> --size <size>`.
|
|
62
|
+
Approvals are capped at 2 GB and never lower a creator below the default.
|
|
63
|
+
|
|
54
64
|
For team projects, Lumine mirrors the website workspace flow: choosing or
|
|
55
65
|
pulling the owner's main project creates or reuses your contribution branch and
|
|
56
66
|
checks out that branch locally. Saves go to your branch, so the project owner
|
|
@@ -128,6 +138,27 @@ Discovery is static and fail-closed: runtime code cannot add tools that were
|
|
|
128
138
|
not declared in the pinned manifest, and a session refuses to connect if any
|
|
129
139
|
declared handler is missing.
|
|
130
140
|
|
|
141
|
+
### Connecting to a tab you already have open
|
|
142
|
+
|
|
143
|
+
In an app that offers tools, a signed-in viewer can click **Connect AI helper**
|
|
144
|
+
in the app toolbar (or the workspace preview toolbar). Twinkle shows a
|
|
145
|
+
six-character code for that open tab, valid for 10 minutes and usable once.
|
|
146
|
+
Then run:
|
|
147
|
+
|
|
148
|
+
```bash
|
|
149
|
+
lumine app-mcp <app-url-or-id> --code ABC123
|
|
150
|
+
```
|
|
151
|
+
|
|
152
|
+
The bridge attaches to that tab instead of opening a new one. The CLI must be
|
|
153
|
+
logged in as the same Twinkle account as the tab. The tab shows an
|
|
154
|
+
"AI helper connected" badge with a **Disconnect** button and an **Allow edits**
|
|
155
|
+
switch, which starts off: until the viewer switches it on, only tools declared
|
|
156
|
+
read-only in `/app-tools.json` (`"readOnly": true`, or
|
|
157
|
+
`"readOnlyWhen": { "action": ["list"] }` for one action argument) work.
|
|
158
|
+
Undeclared tools count as edits. Disconnecting, or leaving the app, ends the
|
|
159
|
+
session and resets the switch. `--helper-name <name>` overrides the label the
|
|
160
|
+
viewer sees (by default the MCP client's own name).
|
|
161
|
+
|
|
131
162
|
## Inspecting Build SDK data
|
|
132
163
|
|
|
133
164
|
`lumine sdk call <namespace.method> '<jsonArgs>'` calls a build's data SDK
|