Commit Graph

7 Commits

Author SHA1 Message Date
33ca457e03 fix: 0.6.1 - badge said 5 layers, there are 6
The status bar had "5 layers ready" hardcoded from before the anti-censorship
layer existed. Replaced all 4 occurrences with 6, and the tooltip now says
six prompt layers including output anti-censorship. The profile tool's design
array was also corrected.

Verified after restart:
  version 0.6.0 loaded, six layers all enabled
  permission.effective = overridden-by-user-layer (expected: profile wins)
  environment.hardConflicts = [], softOverlaps = [dsh-purge: system-prompt]
  provider deepseek-account/deepseek-flash, censorRisk medium
  update current 0.6.0 / latest v0.6.0 / up to date
  skills 63 total, 48 ready
  badge renders "六层就绪 · 权限由用户层接管" in amber (correct)
2026-11-17 15:27:56 +08:00
4b9eb3c1ff feat: 0.6.0 - update check and one-command upgrade
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).
2026-11-17 15:14:23 +08:00
2c50d1e79e feat: 0.4.3 - precise conflict detection (read actual config ids, not package names)
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.
2026-11-17 14:53:13 +08:00
773a1840e9 feat: 0.4.0 - sixth layer (output anti-censorship) + provider censor-risk probe
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.
2026-11-17 14:33:27 +08:00
83ceae9e72 feat: 0.3.0 - let the plugin diagnose itself
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)
2026-11-17 14:28:01 +08:00
1885e1368d feat: 0.2.0 - built-in permission layer (sandbox, approval, no truncation) via official config overrides only 2026-11-16 14:31:51 +08:00
3e9971feb7 feat: moyun-ultimate 0.1.0 - five-layer layered prompt core
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.
2026-11-16 14:23:46 +08:00