Add dev-report plugin (Documentation)

[delpicorp]

Adds dev-report to the Documentation section, vendored under plugins/dev-report/ to match how every other plugin in this repo is listed. Also added to README-zh.md.

What it does

You finish a long Claude Code session. A dozen files changed and several implementation decisions were made along the way, but the end-of-session summary is file names and function names — accurate, and written for someone reading the diff alongside it. Asking for it "simply" removes the reasoning too.

/dev-report explains the session in plain language instead:

• what was built or changed, in terms of the product rather than the file tree
• why that approach was chosen, including the option that was rejected and what would have gone wrong
• what is still unfinished or unverified — verified, assumed, and untested kept apart
• what to do next, and which calls are the user's to make

Technical terms aren't stripped out — they're explained the moment they first appear, so the reasoning survives.

What's in the folder

plugins/dev-report/
├── .claude-plugin/plugin.json
├── README.md            # description + attribution
├── SKILL.md             # the skill itself
├── commands/            # /dev-report + ko · ja · es aliases
├── references/          # craft.md, examples.md (two worked example reports)
└── LICENSE              # MIT

Markdown only — no agents, hooks, scripts, or MCP servers. About 380 always-on tokens. Explicit-only, so it does not fire on a casual "what did you just do?". Reports come out in whatever language the command was typed in.

Attribution

Original: delpicorp/dev-report, MIT. Vendored unmodified at v1.0.1 except for the folder README and a plugin.json trimmed to the fields this repo uses. Attribution and the upstream marketplace install are both in plugins/dev-report/README.md, so anyone wanting updates can install from source. Disclosure: I'm the author.

Happy to move it to a different category if Documentation isn't the right fit.