[antianqi]

Why

Two things stand between this package and the MiniMax Marketplace.

1. The manifest does not match the Marketplace's own rules. The official
submission guide (Plugin Development and Submission Guide)
says production publishing takes icon only — "omit darkIcon entirely,
including empty or null values" — and takes 0–3 example queries. The
package declared a darkIcon and shipped five queries, so the guide's own
rejection list ("Plugin name, version, paths, JSON Schema ... does not comply
with the specification") applies.

2. The package has no picture of itself. Every Mini App the team has
picked for the marketplace carries a screenshot of the running app — the
community repository's own plugins put theirs in docs/preview.png and show
them under the title. This one had none, and a reviewer cannot judge a canvas
from a paragraph.

What changes

Six files:

File	Change
.minimax-plugin/plugin.json	darkIcon removed; exampleQueries cut from 5 to 3; version 0.84.0 → 0.86.0
package.json	version 0.84.0 → 0.86.0
docs/preview.png	new — the picture-replication template on the board: a reference picture goes in, the prompt is read back out of that picture, and a new picture is made from the prompt
docs/templates.png	new — the template panel: 图片复刻 and 视频模仿, plus the five shapes of H3
README.md	the picture under the title, the author and the version, and a note that the preview uses synthetic data
README.zh-CN.md	the same, in Chinese

The version goes up because the package content changed, which is what the
guide asks for.

The three queries that are kept are the ones a stranger can act on: open the
canvas by name, make a picture on it, and turn a picture from the canvas into
a grid. "把这两个节点连起来" and "用提示词增强写一条 H3 视频提示词" are gone —
the first one has no subject when it is read on its own.

Both pictures use synthetic material: a canvas of our own with the built-in
template on it, and no data of any user. The canvas, the MCP server and the
skill are the same bytes as 0.84.0 — only what the package says about itself
changed.

Verification

• 248 unit tests, all green (node --test tests/*.test.mjs)
• 248 mutation self-checks, all green — every contract was broken on
  purpose and the test had to turn red (the script lives outside the package,
  it is the checker's own harness)
• Static guards: no undefined references, no self-referencing declarations
• The repository's own check: npm run check → 69/69, exit 0;
  npm run validate → plugins/antianqi/ai-node-canvas: 0 errors, 1 warning
  (HOST_CONNECTOR_UNVERIFIED — the Host grants the declared providers at
  install time) and repository: OK
• A pre-submission audit of our own, run against the ZIP the way the
  Marketplace guide describes the package: 37 rules (archive shape, byte-for-byte
  against the source, encoding, manifest fields, Skill frontmatter, MCP schema,
  install scripts, README headings, licence, credential sweep) — 0 failures.
  The script also has a negative control: a package broken on purpose turns it
  red on 20 rules.
• On the real host (build 269afb3ce884): published and opened, the user's
  own canvas loads with its four nodes, the template panel and the 「能力清单」
  panel open and close, no error in the console