feat(pi.session-orchestrator): release 0.6.1 with usage triggers and quick start

[muzimu217]

Why

Upstream issue #50 asks how pi.session-orchestrator is used — twice. After installing, the plugin shows no panel and no command, and nothing in the shipped SessionTask tool description or README told users (a) that it lives entirely inside Agent chat, or (b) that no special keyword is needed to trigger it. The maintainer's answer ("just ask it to open a sub-session") never reached the README or the tool description, so every future user hits the same wall.

What changed

• Tool description (manifest.json): leads with explicit when-to-use trigger conditions — parallel work, spawning sub-sessions/workers, delegation, follow-ups — including example phrasings in Chinese and English, plus a negative scope ("Not for ordinary single-session chat"). This mirrors how official plugin/skill descriptions are written (capability summary + Use when… + examples + negative scope), so the model picks the tool up from the user's goal without magic keywords.
• README: adds a bilingual Quick start (how do I use it?) section right after Install — states there is no panel/command/config, gives three example prompts with what actually happens, and tells users what to say if the agent still misses the tool.
• Version 0.6.0 → 0.6.1 (docs/description-level change), changelog updated, test version assertion updated.

Verification

python3 scripts/pack_plugin.py plugins/pi.session-orchestrator   # OK, sha256 7504d4b9…88b8, 52965 bytes
python3 scripts/security_audit.py --check-packages               # passed, no blockers
python3 scripts/rebuild_catalog.py                               # OK, 25 plugins
node --test tests/*.test.mjs                                     # 181 pass, 0 fail (1 platform skip, pre-existing)
unzip -p packages/pi.session-orchestrator-0.6.1.piplug manifest.json  # ships 0.6.1 with the new description

The test harness loads main.js with a mocked host and asserts registration uses the exact manifest descriptor, so the shipped schema and the registered tool stay in sync.

Closes #50

[vercel]

@muzimu217 is attempting to deploy a commit to the vastsa's projects Team on Vercel.

A member of the Team first needs to authorize it.

[vastsa]

https://github.com/vastsa/pi-plugin-session-orchestrator
插件编排移到这个仓库啦，辛苦 pr 到这里哦

[muzimu217]

好的好的，我明白了。抱歉，刚刚的情况——我们没注意到插件源码正在迁到各作者的独立仓库，还按老方式往这个市场仓库提了 PR，不好意思。之后 session-orchestrator 的改动我们直接提到 pi-plugin-session-orchestrator 那边。谢谢说明！