@yuchaocheng/yusijia 0.1.0-beta.2 → 0.1.0

package/README.md

@@ -11,13 +11,12 @@ scans require `/usr/bin/unzip` and fail clearly when unavailable.
 
 ## Installation
 
-The package is `@yuchaocheng/yusijia`. This is a beta release for acceptance testing,
-not a stable release. The hosted website's new Agent API is not yet released;
-use an explicitly supplied compatible development site for this beta. Installing
-the beta does not deploy a website or automatically switch the default site.
+The stable package is `@yuchaocheng/yusijia`. Normal family use connects to
+`https://yusijia.me`; development testing requires an explicitly supplied local site.
+Installing or updating the CLI does not deploy a website or switch its default site.
 
 ```sh
-npm install --global @yuchaocheng/yusijia@beta --registry=https://registry.npmjs.org/
+npm install --global @yuchaocheng/yusijia --registry=https://registry.npmjs.org/
 yusijia --help
 yusijia skills install
 ```
@@ -31,15 +30,16 @@ requests need only the family task and supplied material, not installation steps
 First setup can be delegated to an Agent: install this public package, run
 `yusijia skills install`, and check host discovery. Beta versions of
 `yusijia update` stay on the `beta` tag; stable versions use `latest`. Updates never
-fall back between channels. No stable version has been published; unversioned
-installs may also resolve to a beta, so acceptance installs must select `@beta`.
+fall back between channels. Existing beta installations must explicitly install
+`@latest` to switch to stable releases. Production requires a stable CLI; beta
+versions are for explicitly selected compatible development sites.
 
 Build and test a local tarball (not a release):
 
 ```sh
 pnpm -C family-cli build
 npm pack ./family-cli --pack-destination ./family-cli
-npm install --global /absolute/path/yuchaocheng-yusijia-0.1.0-beta.2.tgz
+npm install --global /absolute/path/yuchaocheng-yusijia-0.1.0.tgz
 yusijia --help
 yusijia skills install
 ```

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@yuchaocheng/yusijia",
-  "version": "0.1.0-beta.2",
+  "version": "0.1.0",
   "description": "Family content CLI and Agent Skill for photos, albums, timelines and diaries",
   "license": "UNLICENSED",
-  "publishConfig": { "access": "public", "tag": "beta", "registry": "https://registry.npmjs.org/" },
+  "publishConfig": { "access": "public", "tag": "latest", "registry": "https://registry.npmjs.org/" },
   "type": "module",
   "bin": { "yusijia": "dist/cli.js" },
   "engines": { "node": ">=20.20.2" },

package/skills/family-content/SKILL.md

@@ -118,6 +118,36 @@ Never flatten an existing rich document or remove images/tables without consent.
 Unsupported edits must stop and leave the website editor as the alternative.
 Timeline allows at most three photos. Album remove only removes associations.
 
+## Completion
+
+After successful writes, read back the affected objects using the site's `get`
+commands and compare them with the confirmed content. Report any mismatch or
+unverified result honestly; an execute success is not a visual check.
+
+Give clickable website viewing links using the confirmed plan origin and actual
+result/target IDs, encoding each ID as a URL path segment. These are the supported
+viewing routes; do not guess other detail paths:
+
+| Result | Website path |
+| --- | --- |
+| Album | `/photos/albums/<albumId>` |
+| Photos without an album | `/photos` |
+| Growth event | `/timeline` (identify the event by date and title) |
+| Diary | `/diary/<diaryId>` |
+
+Do not substitute signed OSS URLs, API endpoints or local progress files for
+website viewing links. Never replace an explicit local site with the default
+production site. Link only successful, readable results, not failed or unknown
+items; use Recovery for partial outcomes.
+
+Ask the user to open these links and confirm the displayed photos, dates, wording
+and associations look right. This is a visual review, not another approval to repeat writes.
+Do not claim browser rendering was verified unless it was actually checked.
+Keep the final reply focused on saved content, viewing links and this invitation;
+omit plan hashes, Skill quotations and environment notes unless needed for recovery
+or requested by the user. User feedback requiring further writes gets a new preview
+and confirmation, not a silent correction.
+
 ## Recovery
 
 Partial completion is a nonzero exit, not an all-or-nothing rollback. Report each