docs(roadmap): add #411 — plugins enable/disable: no changed flag; reload_runtime always true

[code-yeongyu]

Pinpoint #411

plugins enable/disable --output-format json always emits reload_runtime:true even on no-op re-enable/disable, and omits previous_status, changed, version, source fields. Plugin state is only available by scraping the prose message column table.

Evidence:

// Already-enabled plugin re-enabled:
{"action":"enable","kind":"plugin","message":"Plugins\n  Result           enabled example-bundled@bundled\n...","reload_runtime":true,"target":"example-bundled"}
// No changed field, no previous_status, reload_runtime always true

ROADMAP-only PR. No source/test changes.

[Yeachan-Heo]

Review verdict: APPROVE

Checked exact diff origin/main...origin/pr/2955: docs-only ROADMAP.md change (+2), no source/test/schema/runtime contract changes. CI is green and GitHub merge state is CLEAN.

The #411 pinpoint is concrete and non-duplicative relative to nearby plugin lifecycle items:

• 跟~合影留恋！名昊教育飘过 #348 covers prose-only plugin list inventory
• 合影留念 #349 covers unsupported plugins show
• 量化、A股相关Skill 加微信：endofworld42 #350 covers missing-plugin enable hang
• 合影 #351–合影 #353 cover missing-target disable/update/uninstall stderr/generic errors
• Niubility overflow #411 specifically covers idempotent plugins enable/disable --output-format json response shape, missing changed/previous_status metadata, and incorrect reload signaling.

Merge risk: low. Blockers: none.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]