Pin the extension roadmap and downstream spike

Why: Downstream products need a published extension surface, contract checks, and a sample plugin that does not modify the base.
Evidence: scripts/lint-boundaries.sh printed boundaries ok. examples/downstream-rdm go test passed. Submodule pointers record the core, documents, backend, ui, and frontend commits for this roadmap.
Impact: make test runs the boundary lint first. make plugin-new scaffolds a declaration plugin. Version tags and remote downstream repositories are not created.
Refs: .task/feature-base-extension-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>

This commit is contained in:

weichen

2026-10-01 10:35:15 +00:00

co-authored by

Cursor

parent ea0382a28f

commit 09964e522b

21 changed files with 182 additions and 11 deletions

									
										examples/plugins/decl-demo/knowledge/notes.json
									
		+1
		
												View File
												
				@@ -0,0 +1 @@

				{ "id": "notes", "title": "笔记", "description": "数据集声明，检索引擎在基座" }

				`@@ -0,0 +1 @@`
				`{ "id": "notes", "title": "笔记", "description": "数据集声明，检索引擎在基座" }`