T

weichenandCursor a0da588f90 Document the base extension roadmap and plugin contract v2

Why: The base must stay unmodified by downstream products, so the roadmap, compatibility window, and plugin contract need a written proposal before further forks.
Evidence: Three proposals under docs/proposals and a short pointer in the plugin development guide.
Impact: Downstream work follows extension-point requests and a published base version. Tag commands in the compat proposal are not executed.
Refs: .task/feature-base-extension-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>

2026-10-01 10:34:30 +00:00

docs

Document the base extension roadmap and plugin contract v2

2026-10-01 10:34:30 +00:00

.gitignore

Ignore local mimosa hook status artifacts

2026-09-30 16:15:59 +00:00

AGENTS.md

Record Gitea access facts in AGENTS.md

2026-09-30 16:06:17 +00:00

README.md

Add the 0.1.0 usage report