Development

[waynebaby]

This pull request significantly updates the documentation for the loom-skill-enhancement skill, clarifying and strengthening the requirements and workflow for skills governed by the Loom Skill Orchestrator (previously referred to as "SO"). The changes emphasize explicit user choices, stricter governance, and improved workflow template standards, especially for skills that are already enhanced by Loom Skill Orchestrator. The terminology throughout the documentation has also been made more consistent and precise.

Key documentation and process improvements:

Loom Skill Orchestrator Governance and Upgrade Process

• All references to "SO" have been replaced with "Loom Skill Orchestrator" for clarity and consistency. The documentation now clearly distinguishes between "SO-enhanced" and "SO-exclusive governance mode", and introduces stricter rules for re-enhancing already-governed skills, including a mandatory user prompt to select between the latest released or beta package before proceeding. [1] [2]
• The process for re-enhancing an already-governed skill now requires reacquiring the package from the user-selected channel, running dotnet so.dll --guide [--lang <language>] as mandatory authority input, and recording the user's explicit package channel/version choice. Silent reuse of previous lock channels/versions is now forbidden.

Workflow Template Standards

• New requirements are added for workflow templates: all steps must be explicit, and generic "multistep plan" nodes are disallowed. Templates must model governed steps, guards, seams, and reviewable outputs, and must not hide open-ended execution behind planner nodes. [1] [2]

Completion and Validation Criteria

• The completion criteria and forbidden results sections have been expanded to require explicit evidence of user-confirmed package selection and a fresh guide run for re-enhancements. The documentation now explicitly forbids results that imply optionality or dual-track governance, or that use generic planner nodes in workflow templates. [1] [2]

Terminology and Consistency

• All references, examples, and output contracts now use "Loom Skill Orchestrator" terminology, ensuring consistency across the documentation and aligning with the updated governance model. [1] [2]

These updates ensure that skill enhancements using Loom Skill Orchestrator are more deterministic, user-driven, and compliant with explicit governance and workflow standards.

[waynebaby]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Merge conflicts have been resolved. The conflicts were in README.md and README.zh-CN.md in the release notes section — both files had conflicting version headers (v0.2.77-beta from development vs v0.2.77 from main) and package version lists. Resolved by keeping the beta release notes from the development branch.