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
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)
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.