@seeed-studio/sensecraft-cli 0.4.5 → 0.4.6

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@seeed-studio/sensecraft-cli",
3
- "version": "0.4.5",
3
+ "version": "0.4.6",
4
4
  "description": "SenseCAP / SenseCraft AI cloud CLI (devices, apps, models, files, cloud deploy)",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -46,7 +46,7 @@ Read the applicable references in the table **before** doing each part. Build ev
46
46
 
47
47
  **App information.** Read [app-fields.md](../references/app-fields.md) in full before synthesizing these fields, including its activity selection guidance. Keep the project's name unless the user chooses a change. Write an excerpt for the intended reader: what it does, who uses it, and the useful outcome. Propose a scene label and its real ID from `app_scenarios_array`. Preserve known choices for `allow_clone` and `allow_commerce`; if unknown, ask rather than inherit template defaults or infer permissions from the license. Resolve author from the authenticated account when established; identify the project license separately. Inspect cover/gallery candidates and keep their order explicit. No cover is allowed for a private draft; note the publishing requirement.
48
48
 
49
- **Activity participation.** Use the project understanding from discovery and follow [app-fields.md § Activity selection](../references/app-fields.md#activity-selection-during-app-authoring) to decide whether to join an activity. Record the resolved selection in `info.activity_id` and the rationale in the review.
49
+ **Activity participation.** Whether to join, and which activity, is the user's decision: present the candidates from discovery with a recommendation and ask. Follow [app-fields.md § Activity selection](../references/app-fields.md#activity-selection-during-app-authoring). Record the user's selection in `info.activity_id` and the rationale in the review.
50
50
 
51
51
  **Deployment.** Read all of [tool-blocks.md](../references/tool-blocks.md), then map the complete first-time user journey to its supported blocks. For each action, record prerequisites, the chosen tool, verified config/artifact source, and the observable result. Inspect real artifact existence, target/architecture, build configuration, and required runtime inputs. A firmware file does not establish a model-deploy step; source code alone does not establish a flashable image. Place each tool directly after its instructions in a flat `deployment.blocks` array.
52
52
 
@@ -58,7 +58,7 @@ Record the query and selected result in review notes. Multiple plausible variant
58
58
 
59
59
  ## 3. Resolve uncertain decisions
60
60
 
61
- Present a concise project summary, proposed fields, activity selection or reason for none, deployment actions/tools, BOM matches, and actual gaps. Batch questions about consequential choices: name/language/audience when unclear, scene, clone/commercial permissions, uncertain activity eligibility/selection, hardware variant and BOM scope/quantity, assets, or an unsupported deployment path. Include a recommendation and why; reuse answers already in the conversation.
61
+ Present a concise project summary, proposed fields, activity candidates with a recommendation, deployment actions/tools, BOM matches, and actual gaps. Batch questions about consequential choices: name/language/audience when unclear, scene, clone/commercial permissions, activity choice (join which activity or none), hardware variant and BOM scope/quantity, assets, or an unsupported deployment path. Include a recommendation and why; reuse answers already in the conversation.
62
62
 
63
63
  Ask only for uncertainty that affects correctness or the user's choice. Do not require an arbitrary one-round limit: a new material conflict can need a follow-up. Continue independent preparation while waiting, but do not commit guessed decisions or perform dependent uploads. Review is not an extra approval gate when the requested creation and all necessary decisions are already authorized.
64
64
 
@@ -94,7 +94,7 @@ Update the review notes with corrections, evidence, remaining gaps, and readines
94
94
 
95
95
  1. Read the upload references. Run `sensecraft-cli auth info`. If no Access Key is active, use the split `auth init` flow in [`../SKILL.md`](../SKILL.md). Do not run bare `auth init`. Recheck the environment and that selected files still match their reviewed hashes. Upload only reviewed assets; reuse unchanged URLs. Images: `file upload --path <image> --type 1 --for-app`. Firmware: `--type 4`. Other artifacts: select the actual type/flags from the reference. App images use at most 16 JPG/JPEG/PNG/GIF/WebP files, each ≤5 MB; other artifacts are ≤100 MB.
96
96
 
97
- For Muse firmware, scan the exact file selected for upload before `file upload --type 4`. A complete SDK token is `mgst_` followed by 43 characters from `[A-Za-z0-9_-]`. The short `mgst_` prefix used by firmware format validation is not a credential match. Keep the scan quiet so matching values stay local:
97
+ For Muse Gadget firmware, scan the exact file selected for upload before `file upload --type 4`. A complete SDK token is `mgst_` followed by 43 characters from `[A-Za-z0-9_-]`. The short `mgst_` prefix used by firmware format validation is not a credential match. Keep the scan quiet so matching values stay local:
98
98
 
99
99
  ```bash
100
100
  grep -aqE 'mgst_[A-Za-z0-9_-]{43}' <firmware-file>
@@ -44,11 +44,11 @@ When docs and code disagree, inspect enough to identify the conflict. Use establ
44
44
 
45
45
  ## Ask after discovery has made the choice concrete
46
46
 
47
- Read the field and tool-block references before proposing options. After discovery, run `app activity list` and read the guides/rules for plausible activities per [app-fields.md](../../references/app-fields.md#activity-selection-during-app-authoring); the public activity list does not need an Access Key. Use the gathered project facts to choose a clear fit or none, and ask only when the fit or choice is uncertain. After the agent establishes auth, resolve scene IDs and BOM catalog candidates through the real CLI reads. Record the queries, selected results, source links, and lookup time; offline/sandbox data is not live confirmation. Then batch remaining decisions with a recommendation and a short reason. Typical questions concern:
47
+ Read the field and tool-block references before proposing options. After discovery, run `app activity list` and read the guides/rules for plausible activities per [app-fields.md](../../references/app-fields.md#activity-selection-during-app-authoring); the public activity list does not need an Access Key. Use the gathered project facts to rank the candidates, then ask the user to choose an activity or none. After the agent establishes auth, resolve scene IDs and BOM catalog candidates through the real CLI reads. Record the queries, selected results, source links, and lookup time; offline/sandbox data is not live confirmation. Then batch remaining decisions with a recommendation and a short reason. Typical questions concern:
48
48
 
49
49
  - Product framing or language when the conversation and project do not establish it.
50
50
  - Clone and commercial-use choices; a project license alone does not answer these platform settings.
51
- - Activity options plus no participation when eligibility, missing requirements, or the best candidate is uncertain. Include actual dates, rules and project fit; do not ask a generic opt-in question for every new app.
51
+ - Activity choice for every new app: which candidate to join, or none. Include actual dates, rules, fit and gaps, and a recommendation; never ask a generic opt-in question without candidates.
52
52
  - Similar hardware variants, optional accessories, unknown quantities, or a custom product fallback.
53
53
  - Missing deployable files, an unsupported action, or a choice to upload an explicitly incomplete draft.
54
54
  - Cover selection or an asset with unclear redistribution rights.
@@ -206,7 +206,7 @@ sensecraft-cli app delete --id <app_id> --yes
206
206
  sensecraft-cli app activity list
207
207
  ```
208
208
 
209
- The returned `guide_url` is the source for requirements and official rules; requirements are not included as a structured CLI field. Read candidate guides and compare them with the project before selecting an activity. Follow [activity selection during authoring](app-fields.md#activity-selection-during-app-authoring) for choosing a match, choosing none, or asking the user with options. Do not confuse `priority_activity_id` (list ordering) with `activity_id` (joining).
209
+ The returned `guide_url` is the source for requirements and official rules; requirements are not included as a structured CLI field. Read candidate guides and compare them with the project before selecting an activity. Follow [activity selection during authoring](app-fields.md#activity-selection-during-app-authoring) for presenting the candidates, no-activity option, and recommendation that the user chooses from. Do not confuse `priority_activity_id` (list ordering) with `activity_id` (joining).
210
210
 
211
211
  ### `app like` / `app unlike` / `app collect` / `app uncollect` / `app mark-deploy` (L2)
212
212
 
@@ -33,9 +33,9 @@ Read [the activity command reference](app-commands.md#app-activity-list) before
33
33
 
34
34
  Compare the documented theme, entry window/deadline, eligibility, supported/required hardware or features, required artifacts/demo/docs, and licensing/clone/commercial conditions with the actual project and settled user choices. Distinguish what the project already satisfies from deliverables still needed. A successful empty list means no currently available activity; a failed request is not an empty list. Sandbox output is not a live activity or eligibility check.
35
35
 
36
- - **Clear suitable activity:** select it with a concise evidence-based reason. If several qualify and one is clearly preferable for this project, explain that choice. Do not use result order or a popular-list `priority_activity_id` as the entry decision.
37
- - **No suitable activity:** select no participation and explain the mismatch or lack of open activities. Omit `activity_id`; do not use `0`, invent an ID, or ask a redundant opt-in question when the evidence supports the decision.
38
- - **Uncertain choice or eligibility:** ask with concrete options: candidate names/IDs, dates with a timezone, important requirements and project fit/gaps, plus **no activity**. Recommend the best-supported option. Reuse known answers. Do not change the project's agreed permissions or invent missing eligibility facts to make an entry fit. If new permission choices or required consent are unresolved, ask about those with the activity options.
36
+ - **Always ask the user.** Never choose participation here, even when one candidate is an obvious fit: whether to join and which activity are the user's decision. Ask with concrete options: each candidate's name and ID, its window with a timezone, the requirements and fit gaps that matter, plus **no activity**. Recommend the best-supported option and say why. Never use result order or a popular-list `priority_activity_id` as the recommendation.
37
+ - **Empty list:** no activity is open, so nothing can be joined; report it and continue without one. A failed request is not an empty list.
38
+ - **Unverified eligibility:** ask with the same options and name what is unverified. Do not change the project's agreed permissions or invent missing eligibility facts to make an entry fit; unresolved permission or consent choices belong in the same question.
39
39
 
40
40
  Record the chosen activity or no-activity reason, lookup time, API/guide sources, applicable rules, and project evidence in local review notes. For `create-app`, store the optional selection in `info.activity_id` and include its positive integer at payload top level on the initial one-shot create; the CLI applies it in the new app's follow-up save. Always send the resolved `allow_clone` explicitly: the CLI may otherwise turn it on when joining an activity. An explicit `allow_clone: 0` is technically preserved by the CLI, but does not establish eligibility for a contest requiring cloning.
41
41