FR: entity alias management + advisory ack-list (feedback from a real-world setup)

[VibeSan7]

Two feature requests after running a full Russian-language vault on
Windows end-to-end (code project → docs → Synto → MCP → Claude Code).

1) No CLI way to remove a wrong alias from an entity.
In our vault the fast model attached the npm package name
@mocha/engine to the project entity (name similarity). merge is
wrong here (genuinely different concepts), split is heavy for a
one-alias fix. Suggest:

synto concept alias remove <ENTITY> <ALIAS>

(plus alias add / alias move).

2) Advisory ack-list.
Known-and-accepted advisories (graph_noise which is true by construction,
protected pages, the code-block false positive I filed separately)
permanently occupy maintain output, so new issues hide inside a
familiar baseline. Suggest synto maintain --ack <check>[:<path>] or an
[ack] section in synto.toml, with acked items collapsed into a
one-line count.

Aside: the escalation pass after truncation, protected pages for
manual edits, and the merge preview+confirm flow are genuinely well
designed — the pipeline survived a full Russian-language vault on
Windows end-to-end. Thanks for the project.

Env: Synto 0.6.2, Python 3.14, Windows 11 (ru-RU).

[kytmanov]

Thanks a lot for the feedback! Really useful to hear from a full end-to-end setup.

Both suggestions make sense. I'll improve concept alias management and add a way to acknowledge/suppress known advisories in maintain for the next release.

Glad the pipeline held up on a Russian Windows vault. On the Synto → MCP → Claude Code path: what worked well for you there and where did it still fall short or need workarounds?