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.