Answers: when I ship a new version, how does the user find out, and what do
they do about it.
Three ways to learn:
1. moyun_ultimate_profile now returns an update block: current, latest,
available, notes, howTo, page.
2. New tool moyun_check_update (force: true re-queries).
3. On startup the plugin checks the latest release in the background and logs
a line when a newer version exists.
One command to upgrade:
powershell -ExecutionPolicy Bypass -File .\update.ps1
It queries the release, downloads the tgz, backs up the current directories as
*.bak-update-<stamp>, extracts over them, and PRESERVES the user's mode choice
(complement stays complement, it is not clobbered into full).
Variants: -Check (report only), -Force (reinstall), -DryRun (dry run).
Opt out with checkUpdate: false in the bundle patch.
Version comparison is numeric per segment so 0.10.0 > 0.9.9. Network failure
degrades quietly; startup is not blocked (8s timeout, background promise).
The goal is users who dare to install it. Three additions:
1. doctor.ps1 -Fix
Runs the 12 checks, then repairs what is safe to repair: re-copy the runtime
copy, add exports["./client"], add the dependencies entry, sync missing
skills. It deliberately does NOT touch the profile's own cordis.patch.yml
(that could break other plugins) - it only prints a hint.
2. install.ps1 -Rollback
Restores package.json from the newest package.json.bak-* and removes the
plugin directories. One command back to the pre-install state.
3. Friendly install ending
Prints the three next steps (quit/reopen, doctor, moyun_ultimate_profile)
plus the two escape commands, instead of a single terse line.
doctor also detects and reports whether the install is in FULL or COMPLEMENT
mode by reading the bundle patch, so complement mode is no longer misreported.
Instead of removing other people's plugins (which breaks their environment and
cannot be rolled back), this detects and yields.
1. install.ps1 scans every installed bundle before copying, reads the config ids
each one actually rewrites, and intersects with ours:
scanned plugins : 19
hard conflicts : none
~ dsh-purge shares: system-prompt (safe)
2. Three modes. auto (default) picks complement when a hard conflict exists,
full otherwise.
full permission layer owned by this plugin
complement permission layer yields, prompt layers + 63 skills still apply
auto decided by the scan
3. switch-mode.ps1 flips between them at any time; the full patch is kept as
cordis.patch.yml.full so switching back is one command.
New file cordis.patch.complement.yml drops the five permission-related config
overrides entirely, so coexistence is structural rather than hopeful.
Deliberately NOT doing: uninstalling other plugins. Reasons are in the README.
The old heuristic matched names like purge|ungate|jailbreak and reported
dsh-purge as a sibling. That was wrong: dsh-purge patches host source, it does
not touch approval/permission config ids at all.
Now the plugin reads every installed bundle's cordis.patch.yml, extracts the
config ids it actually rewrites, and intersects with its own set:
hardConflicts - other plugin rewrites approval/permission/sandbox-policy/...
-> last-applied wins, one silently stops working -> pick one
softOverlaps - other plugin only rewrites system-prompt (identity prefix)
-> negligible difference -> safe to coexist
Measured on this machine (22 bundles): scanned 19, hardConflicts [],
softOverlaps [{dsh-purge, system-prompt}]. So dsh-purge and this plugin do NOT
conflict.
Eleven comments from the video, each marked resolved / partially resolved /
cannot be resolved, with a pointer to the file that handles it.
Honest status:
- 9 resolved (install, verify, purge conflict, "second fork", missing binaries,
model gets dumber, not-working)
- 1 partially resolved (safety refusal: host permission fixed, model layer
fixed, server-side moderation improved by provider switch + layer 6 but not
removable)
- 1 cannot be resolved (the one about bypassing limits on minors - out of scope)
When the projection payload (armor) had not arrived yet, permOn evaluated to
false and the badge said the permission layer was closed, even though
config.permission is true. Only trust armor.permissionOn when it is an actual
boolean; otherwise assume on.
Real permission state should be read from moyun_ultimate_profile:
permission.effective = effective | overridden-by-user-layer | disabled-by-config
Server-side output moderation was the one thing the prompt layers could not
touch. This release does the two things that actually work:
1. prompts/50-anticensor.md (order 220, 1663 B): how to tell apart model-layer
refusal from output truncation, and five re-expression strategies that raise
pass rates (code-block form / segmentation / terminology / counterfactual
framing / language mix), plus the correct retry posture (change form, do not
resend verbatim).
2. moyun_ultimate_profile now reports a provider block with censorRisk:
high (ModelScope / Qwen / Zhipu), medium (DeepSeek official), low (overseas),
none (local). Changing provider is usually more effective than rewording, and
now the user can see which class they are on.
Local measurement: modelscope-token-plan + DeepSeek-V4.1-Flash-1017 -> high
(Aliyun content safety, over-blocks technical content).
Six layers total 23,017 B.
Answers the top complaint "it does not work and I cannot tell why" by turning
hidden state into explicit output.
- moyun_ultimate_profile now reports permission.builtin / .effective / .verdict
and environment.profile / .userLayerOverrides / .siblingPlugins / .winner,
so the user can see whether the permission layer actually took effect
- new tool moyun_skills_audit: which of the 63 skills run out of the box and
which are missing their external binaries (nuclei/fscan/IDA/jadx/...)
- badge now colors itself by real state: green (this package owns permission),
amber (user layer overrode it / sibling plugin present / disabled), red (refusal)
- skill audit speed: 2933 ms -> 234 ms by indexing PATH instead of spawning
"where" per command (0 ms once cached)
Answers the issues raised in the comments:
1. "keeps triggering safety refusal" -> README now separates three layers:
host permission (this package fixes it), model willingness (prompt layer),
provider-side moderation (nothing can fix it). TROUBLESHOOTING gives a
decision tree with commands.
2. "how do I verify it worked" -> doctor.ps1 checks 11 items and prints
[OK]/[WARN]/[FAIL]. Verified locally: OK=11 WARN=2 FAIL=0.
3. "does it conflict with purge" -> documented: both target the same config
ids, last-applied wins. doctor warns when a user-layer override or a
conflicting plugin is detected.
4. "incomplete / missing stuff" -> documented that the 63 skills need their
external binaries (nuclei/fscan/IDA/jadx...), which the package does not ship.
5. "stronger armor makes the model dumber" -> confirmed in README as a real
trade-off with per-layer guidance on what to turn off.
Five ordered prompt sections (persona core / refusal kernel / execution
intensity / anti-dilution mirror / skill routing), 63 built-in skills synced
idempotently into DSH_HOME/skills, two tools (moyun_frame, moyun_ultimate_profile),
a live refusal-score badge, and five independent layer toggles.
Ships no host source patches: the permission layer stays with host-patch
plugins, this package owns persona, strategy and skills.