Repository navigation
docs: clarify prepared-reference startup ownership and current Skill specification #133
Description
The current template guide recommends CLI preparation followed by Python launch without explaining that ordinary native deployment may retain its own service startup. This can duplicate a manifest start command. The SDK Skill also says strict specification 4 above its actual specification 5 manifest.
Expected: source users start through unified CLI launch and connect with the SDK; advanced prepared-reference users understand that native/image startup must not duplicate the manifest service. Both languages must agree. Skill prose must say specification 5.
Scope: documentation and engineering records only; no runtime, aliases, preparation mode or package release. Existing bounded official client/server a6 startup and application-auth observation passed, including independent owned-resource absence; do not treat another preparation path as equivalent.
Acceptance: bilingual consumption and authoring guidance, Skill typo, changelog and owner evidence; required exact-head CI/review and normal merge.
Activity
anycodes commentedon Oct 25, 2026
Delivered in normally merged documentation-only PR #134, actual main 676ef04; merge tree independently equals reviewed head 7440407. All 13 exact-head required checks passed, including distributions and both public runtime fixtures.
English/Chinese template consumption, authoring and design overviews now distinguish unified CLI launch followed by SDK connection from advanced Python-owned prepared-reference startup. Native startup must not duplicate the manifest service. The Skill prose matches specification 5. The bounded actual official-a6 startup/auth observation and independent owned cleanup are recorded with their precise scope; earlier failures and evidence are unchanged. No runtime, API, alias, package version or new release changed. Actual closed state independently confirmed.