@mingfuyun/star-allinone 0.4.7 → 0.4.8

package/examples/AGENTS.md

@@ -2,7 +2,7 @@
 
 This is a Umi Max + Ant Design 5 PC admin app. Shared skills live in `.agents/skills/shared-*` and are synced from `@mingfuyun/star-allinone`. Do not edit `shared-*`. Put project-only rules in `.agents/skills/custom-entry/references/` (preferred) or legacy `.agents/project/`.
 
-Always-on instructions are this file. Do not add `.cursor/rules`.
+Always-on instructions are this file. **Normative sources are only this file and `.agents/skills/**`. Do not add `.cursor/rules`.** Do not use global Codex skills under `~/.codex/skills` as a business entry (including retired names such as `publish-starlink-test`, `review-and-commit`, `i-have-adhd`, `zentao-connect`).
 
 Peer React is **18.3.1**. The npm package does not export a table.
 
@@ -17,14 +17,17 @@ Props for `MFProTable` are in `.agents/skills/shared-project-conventions/referen
 
 ## Default workflow
 
-User-facing shared entries only:
+In business repos, dialogue uses **one entry only**: `$custom-entry`. It reads this file and `custom-entry/references/*`, then delegates to `shared-*` or internal `custom-*`. Do not treat direct `$shared-*` as the production entry.
 
-- One endpoint: `pnpm exec star-allinone gen service --operation "METHOD /path/"` or `$shared-api-to-service`.
-- Pages: `$shared-design-to-page`. Standard lists run `pnpm exec star-allinone gen page` inside that skill.
+- Full requirement / end-to-end flow: intent `flow` (orchestrator `shared-dev-flow` when available; until then: output an implementation plan, wait for `确认方案`, then follow the composite order in `$custom-entry`).
+- One endpoint: via `$custom-entry` → `shared-api-to-service`, or `pnpm exec star-allinone gen service --operation "METHOD /path/"`.
+- Pages: via `$custom-entry` → `shared-design-to-page`. Standard lists run `pnpm exec star-allinone gen page` inside that skill.
 - Project health: `pnpm exec star-allinone doctor`.
-- Review and commit: `$shared-review-and-submit`. Wait for confirmation.
-- Test publish: `$shared-publish-test` after explicit pipeline confirmation.
-- Tracking: `$shared-tracking`. Load the SDK from OSS. Do not commit `tracking-sdk.global.min.js`.
+- Review and commit: via `$custom-entry` → `shared-review-and-submit`. Wait for confirmation (`确认提交` / `确认提交并推送`).
+- Test publish: via `$custom-entry` → `shared-publish-test` after explicit pipeline confirmation (`确认推送流水线` / `发布测试环境`).
+- Tracking: via `$custom-entry` → `shared-tracking`. Load the SDK from OSS. Do not commit `tracking-sdk.global.min.js`.
+
+This `examples/AGENTS.md` seeds new projects. Prefer aligning production repos to `$custom-entry` as above.
 
 ## Hard rules
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mingfuyun/star-allinone",
-  "version": "0.4.7",
+  "version": "0.4.8",
   "description": "星系运维前端能力包",
   "main": "dist/index.js",
   "bin": {

package/skills/shared/publish-test/SKILL.md

@@ -56,7 +56,7 @@ before or as part of `max build`. Do not treat `pnpm test` as unit tests; in bus
 - Current HEAD is a named branch, not detached.
 - `origin/<branch>` exists and matches local `HEAD`. Push first when it does not.
 - `YUNXIAO_ACCESS_TOKEN` is available. Request approval for the external Yunxiao CLI call.
-- Never print access tokens.
+- If `YUNXIAO_ACCESS_TOKEN` is unset, the publish script loads `~/.codex/secrets/yunxiao.env` in the same shell when that file exists. Do not ask the user to `export` the token. Never print, copy, or paste the token.
 
 ## After the run
 

package/skills/shared/publish-test/scripts/publish-current-branch.sh

@@ -69,6 +69,16 @@ if [[ "$local_commit" != "$remote_commit" ]]; then
   exit 1
 fi
 
+if [[ -z "${YUNXIAO_ACCESS_TOKEN:-}" ]]; then
+  yunxiao_env="${HOME}/.codex/secrets/yunxiao.env"
+  if [[ -f "$yunxiao_env" ]]; then
+    # Load token for this shell only. Do not print file contents.
+    set -a
+    # shellcheck disable=SC1090
+    source "$yunxiao_env"
+    set +a
+  fi
+fi
 if [[ -z "${YUNXIAO_ACCESS_TOKEN:-}" ]]; then
   echo "error: YUNXIAO_ACCESS_TOKEN is unavailable" >&2
   exit 1

package/skills/shared/review-and-submit/SKILL.md

@@ -54,7 +54,7 @@ Then stop and wait. Do not run Git writes.
 
 ## Confirmation gate
 
-Execute the commit phase only after an explicit reply such as `确认` or `确认提交并推送` that authorizes the latest proposal.
+Execute the commit phase only after an explicit reply such as `确认`、`确认提交` or `确认提交并推送` that authorizes the latest proposal.
 
 1. Re-check branch, status, and full diff.
 2. Confirm the review scope did not change.