@petercjl/cloud-hug-style-transfer 0.5.0 → 0.5.1
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/INSTALL.md +16 -0
- package/README.md +14 -26
- package/UPDATE.md +29 -0
- package/capabilities.json +390 -120
- package/lifecycle/engine.mjs +428 -0
- package/lifecycle/notice.mjs +1 -0
- package/lifecycle/validate-release.mjs +18 -0
- package/lifecycle/version.mjs +19 -0
- package/npm/automatic-update.mjs +1 -82
- package/npm/business.mjs +33 -0
- package/npm/cli.mjs +40 -54
- package/npm/integrity.json +8 -6
- package/npm/skills.mjs +8 -101
- package/npm/update.mjs +6 -99
- package/package.json +21 -5
- package/release-integrity.json +100 -0
- package/skills/cloud-hug-style-transfer/SKILL.md +14 -0
- package/skills/cloud-hug-style-transfer/adapters/codex.json +2 -1
- package/skills/cloud-hug-style-transfer/adapters/generic.json +74 -0
- package/skills/cloud-hug-style-transfer/adapters/sealseek.json +2 -1
- package/skills/cloud-hug-style-transfer/adapters/workbuddy.json +2 -1
- package/skills/cloud-hug-style-transfer/capabilities.json +583 -4
- package/skills/cloud-hug-style-transfer/scripts/run.mjs +10 -0
package/INSTALL.md
ADDED
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
# Install for the current Agent
|
|
2
|
+
|
|
3
|
+
User prompt:
|
|
4
|
+
|
|
5
|
+
> 请安装 npm 包 @petercjl/cloud-hug-style-transfer。
|
|
6
|
+
|
|
7
|
+
The current Agent checks Node.js 22+, command execution, file access, its own supported Skill discovery directory and its registration/refresh mechanism. The Agent resolves an exact destination; the package never chooses a host directory. npm success completes the bootstrap CLI phase only, including installations with scripts disabled.
|
|
8
|
+
|
|
9
|
+
Agent execution contract:
|
|
10
|
+
|
|
11
|
+
1. Resolve the installed CLI and verify `version`; run `skill source --json` and read the canonical Skill and `installationLifecycle`.
|
|
12
|
+
2. Run `skill install --agent AGENT --path EXACT_SKILL_DIR --json`. A valid unnamed Agent uses the generic adapter. The destination contains physical copies of all resources, a `.runtime` with the package and its dependencies, and `scripts/run.mjs`. Node.js and declared external services remain prerequisites.
|
|
13
|
+
3. Invoke `node EXACT_SKILL_DIR/scripts/run.mjs version --json`; inspect `skill status` with the same explicit path. Ownership, hashes, version and independent runtime must be current.
|
|
14
|
+
4. Reload/register the Skill using the current host's mechanism and confirm native discovery. The CLI reports `hostDiscovery: pending`; it cannot attest host registration. Report full completion only after that verification.
|
|
15
|
+
|
|
16
|
+
Existing user-owned targets and local edits are preserved. Managed legacy links are backed up and migrated to physical copies. A missing destination stops before package replacement. On partial failure inspect `update operation --path EXACT_SKILL_DIR --json`, then follow UPDATE.md. Service login and paid generation require their own authorization.
|
package/README.md
CHANGED
|
@@ -1,43 +1,31 @@
|
|
|
1
|
-
#
|
|
1
|
+
# @petercjl/cloud-hug-style-transfer
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
把已有商品图片转换为抱抱云朵社的品牌风格,内置品牌、模特和排版素材。
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
面向具备所需执行能力的任意 Agent;Node.js 22+。当前 Agent 识别自己的 Skill 目录、能力与注册方式。
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
## 安装
|
|
8
8
|
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
安装:将下列提示词发送给目标 Agent。
|
|
9
|
+
把下面这句话发送给当前 Agent:
|
|
12
10
|
|
|
13
11
|
> 请安装 npm 包 @petercjl/cloud-hug-style-transfer。
|
|
14
12
|
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
> 用抱抱云朵社风格转换处理所附图片。
|
|
13
|
+
安装同时包含工具、完整 Skill 和独立运行依赖。Agent 核验本地入口、文件与版本,再确认宿主能发现 Skill。
|
|
18
14
|
|
|
19
|
-
|
|
15
|
+
## 更新
|
|
20
16
|
|
|
21
17
|
> 请更新 npm 包 @petercjl/cloud-hug-style-transfer。
|
|
22
18
|
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
> 请为 cloud-hug-style-transfer 开启兼容稳定版本的自动更新。
|
|
26
|
-
|
|
27
|
-
关闭自动更新:
|
|
28
|
-
|
|
29
|
-
> 请关闭 cloud-hug-style-transfer 的自动更新与自动检测。
|
|
30
|
-
|
|
31
|
-
检查:
|
|
19
|
+
每次更新只处理明确选中的当前 Agent,保留自定义元数据与更新前备份。同版本也会检查和修复 Skill。自动检测默认提示;自动安装需要单独授权。
|
|
32
20
|
|
|
33
|
-
|
|
21
|
+
## 使用
|
|
34
22
|
|
|
35
|
-
|
|
23
|
+
附上图片并说明本次用途、输出数量和特殊要求。
|
|
36
24
|
|
|
37
|
-
>
|
|
25
|
+
> 请使用 cloud-hug-style-transfer,按所附图片和本次要求完成处理。
|
|
38
26
|
|
|
39
|
-
|
|
27
|
+
账号、服务访问与付费生成按各自授权执行。安装不授予服务权限。
|
|
40
28
|
|
|
41
|
-
|
|
29
|
+
## Agent 执行合同
|
|
42
30
|
|
|
43
|
-
|
|
31
|
+
[安装合同](INSTALL.md) · [更新与恢复合同](UPDATE.md)。CLI 通过 `skill source --json` 返回规范来源。安装后的 Skill 使用自身 `scripts/run.mjs`,运行代码与依赖位于自身 `.runtime`。宿主适配记录能力差异与实际测试证据,不作为支持白名单。
|
package/UPDATE.md
ADDED
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
# Update for the current Agent
|
|
2
|
+
|
|
3
|
+
User prompt:
|
|
4
|
+
|
|
5
|
+
> 请更新 npm 包 @petercjl/cloud-hug-style-transfer。
|
|
6
|
+
|
|
7
|
+
Resolve the current Agent's exact Skill destination before replacement. Use its local `scripts/run.mjs` as the maintained execution entry. Run `update install --yes --agent AGENT --path EXACT_SKILL_DIR --json`. Only that selected target is touched. The bootstrap npm package is provenance, not the running target's dependency. Source checkouts are Git-owned; parent-managed installations follow their owner.
|
|
8
|
+
|
|
9
|
+
The operation saves the true pre-replacement package, Skill and metadata snapshot, acquires a candidate with real npm into a target-scoped operation directory, verifies identity and dependencies, then activates the selected copy. Same-version updates repair stale or missing resources and receipts; fully current state is verified no-op. Host UI metadata is preserved separately. The Agent verifies the returned local entry, managed hashes and version, reloads the Skill, then confirms host-native discovery.
|
|
10
|
+
|
|
11
|
+
On timeout, disconnect or failure, inspect `update operation --path EXACT_SKILL_DIR --json` before attempting another install. Use `update resume --path EXACT_SKILL_DIR --operation UUID --yes --json` to reuse an acquired candidate and original backup. New installation is refused while a previous update is unresolved. Acquisition failure without a candidate requires explicit inspection; preserve the operation and snapshot. Never discard local edits to force recovery.
|
|
12
|
+
|
|
13
|
+
Automatic checks run at ordinary task entry, default to notification, have a two-second network deadline, a persistent 24-hour cache, offline backoff, a lock and opt-out. `update policy --mode off|notify|auto --yes --path EXACT_SKILL_DIR` controls policy. Automatic installation requires explicit standing authorization, a resolved target, and the same major version (same minor for 0.x). Help, version, source and task-following operations do not check the registry.
|
|
14
|
+
|
|
15
|
+
## Historical migration
|
|
16
|
+
|
|
17
|
+
Legacy `--root PARENT` and explicit `--home AGENT_HOME` resolve only the supplied path. A historical `--mode link` with an explicit destination translates to physical-copy migration. Requests containing only a named Agent cannot safely determine a directory: they stop with TARGET_PATH_REQUIRED. For such older callers, first preserve their true old installation, acquire the new bootstrap package, and explicitly synchronize the resolved current target. An old parent's actions before handoff cannot be retroactively secured by the new receiver; see the package's historical compatibility evidence before claiming that updater path supported.
|
|
18
|
+
|
|
19
|
+
## Verified historical support contract
|
|
20
|
+
|
|
21
|
+
The regression entry `npm run verify:historical` uses immutable published baseline bytes and real npm. Baselines are sealseek-media-cli 0.6.8, cloud-hug-style-transfer 0.5.0, and nano-product-replacement 0.2.1. Media and cloud support explicit-target old updater handoff. Nano 0.2.1 uses a new bootstrap with an explicit destination and explicit legacy package source; its published updater scans named hosts before handoff, so that old automatic route is excluded. Earlier installations use the same explicit migration contract after ownership verification; their original automatic updater behavior is not claimed tested.
|
|
22
|
+
|
|
23
|
+
`skill update --path EXACT_SKILL_DIR --legacy-source OLD_PACKAGE_ROOT --json` verifies the declared owning package and preserves the original installation before copying. `update rollback --path EXACT_SKILL_DIR --operation UUID --yes --json` restores a verified snapshot when the current target has no local edits. Host discovery is checked separately after recovery or rollback.
|
|
24
|
+
|
|
25
|
+
Legacy links require a verifiable owning-package integrity manifest; business edits made through a link are preserved and block replacement. If that old release has no integrity record, verify its exact published archive before choosing an explicit migration source.
|
|
26
|
+
|
|
27
|
+
## Machine consumer contract
|
|
28
|
+
|
|
29
|
+
`skill source --json` and packaged capabilities expose `maintenanceContract` version 1: typed result-field mappings and explicit target option semantics. `--path` and `--target-directory` select the exact Skill directory; the supported legacy `--root` selects its parent and appends the canonical Skill name. Verify the returned target. Status retains boolean `current`/`edited` fields and exposes `up_to_date`, `editedFiles`, integrity verification and recovery actions. A matching current managed receipt can be reused within the same operation; host-native Skill loading completes the separately owned discovery phase. A fully current installation needs no reinstall or duplicate registry/tree checks.
|