Plan #91: Support type::docs across Issue Flow

[nil4u]

Markdown Plan

Open Markdown Plan

• Branch: 91-support-type-docs-across-issue-flow/plan
• Commit: 2b7b86cb42be4578a062b34301f33dc5713d3a61
• Artifact: .issue-flow/issues/91-support-type-docs-across-issue-flow/plan/001-implementation.md
• Format: markdown

Review this artifact in Issue Flow. Review comments and approval are recorded on this PR/MR.

Source issue

• #91 Support type::docs across Issue Flow

Plan file

• .issue-flow/issues/91-support-type-docs-across-issue-flow/plan/001-implementation.md

Summary

• Add type::docs as a managed, mutually exclusive issue type across CLI and GitHub/GitLab provider operations.
• Add the docs issue template and synchronize runtime prompts, skills, documentation, installed assets, and manifest output.
• Preserve the existing plan/build lifecycle while adding docs-specific source, link, example, and command validation guidance.
• Preserve docs in Console projections and expose it as an independent metrics, color, ordering, and drill-down bucket.
• Cover label, CLI, runtime, install, projection, metrics, and UI behavior with unit and integration tests.

Review focus

• Confirm type::docs should reuse the implementation plan/build route rather than introduce dedicated flow or prompt files.
• Confirm the proposed template fields and verification requirements cover documentation and information architecture work.
• Confirm the Console compatibility strategy: no schema or historical relabel migration, one append-only panel-config migration, and natural correction on future provider refresh/events.
• Confirm the proposed label metadata, stack position, and distinct Console color.

[nil4u]

✅ Markdown Plan 已发布：在 Issue Flow 中审阅