docs: the serialized-object Jev ranking acts
Jev's format and reachability are written onto each candidate and the
deserialization skill confirms the most reachable first; without Jev the
candidates are the signatures' own. TypeSafe Jev, Serialized Object Detection,
AI in the Recon Pipeline, Recon Pipeline Workflow, Agent Skills and Mute Rules
updated; settings registry regenerated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: list Insecure deserialization in the Mute Rules kinds table
The node-filter engine already has the vuln.serialized_scan kind; the wiki
"Kinds you can filter" table was missing its row.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
docs: Multi mute, Models by feature and the three-layer Priority Board
Multi mute on Muted Nodes and the Red Zone, Models by feature in Global
Settings and on every feature page that asks for a model, the settings
that retire the per-project CypherFix model, and the Priority Board's
rules, review and decision layers with the MCP review and run tools.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs(mcp): mute and unmute over MCP
- MCP-Server: the three tools; a "mute_findings and unmute_findings: hiding
and revealing findings" section with what bounds an agent that mutes, the
unknown-outcome contract, and review and revert by token; the triage:mute
permission, "always left unticked"; the write bucket and the daily mute
budget; the new never-do and refusal lines; the audit rows.
- Muted Nodes: the Agent (MCP) badge and filter, the Token filter, reverting
one token's mutes, the refusals during an activation, and the brief re-mute
after a scan.
- Mute Rules: an agent's mute is never touched by a rule; an agent releases a
rule's mute only with includeRuleMutes, which records an exemption.
- Data export: muted_token (a token prefix, never the token) travels with the
graph.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: Mute Rules on the MCP surface, kali:exec defaults, regenerate MCP API reference
- MCP-Server: set_finding_verdict is refused on a muted finding; a Mute Rules
apply blocks start_recon and reads as agent_writing; kali:exec defaults.
- Mute-Rules: an MCP verdict cannot release a rule mute.
- MCP-API-Reference regenerated with `npm run docs:mcp`.
- Project-Settings-Registry refreshed.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
docs(mute-rules): presets - save, load and manage, and the preset badge
A Presets section: what a preset holds and what stays with the project,
that loading saves but never applies, the confirmation's warnings, and when
the PRESET badge shows. The header row of the layout table and the table of
contents mention it, and the FAQ covers a renamed preset's old badge name.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
docs: Node Filters is now Mute Rules; screenshots, and both pages checked against the code
- Node-Filters.md renamed to Mute-Rules.md; links in the sidebar, Muted Nodes
and Priority Board follow it.
- Mute Rules: the page layout, value editors, the suggested rules per kind,
why passive CVEs, OSV and malicious packages need an apply to the current
graph, what an apply refuses rather than waits for, exemptions counted per
graph label, list operators on empty lists, and a corrected Locked list.
- Muted Nodes: the three ways in, the allowlist and imported "Muted by"
values, that rule mutes are removed rather than resolved, reloading the
Graph Map after an unmute, filter counts, and the export contents.
- Screenshots of both pages and the Apply dialog, taken on a lab project
with example.com hosts and documentation IPs only.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>