singularity-forge/src/resources/extensions/context7/extension-manifest.json

{
	"id": "context7",
	"name": "Context7",
	"version": "1.0.0",
	"description": "Fetch up-to-date library documentation and code examples from Context7",
	"tier": "bundled",
	"requires": { "platform": ">=2.29.0" },
	"provides": {
		"tools": ["resolve_library", "get_library_docs"],
		"hooks": ["session_start", "session_shutdown"]
	}
}
feat: add extension manifest + registry for user-managed enable/disable (#1238) Every extension gets a declarative extension-manifest.json (id, tier, provides, dependencies). A persistent registry at ~/.gsd/extensions/registry.json tracks enabled/disabled state. `gsd extensions` command family (list, enable, disable, info) lets users manage extensions without touching source code. Registry gate filters disabled extensions in loader.ts and resource-loader.ts before paths reach loadExtensions(). Zero breakage: extensions without manifests default to enabled, fresh installs have an empty registry. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> 2026-03-18 14:12:19 -06:00			`{`
batch: snapshot of in-flight v2 work This commit captures uncommitted modifications that accumulated in the working tree across multiple in-progress workstreams. It is a snapshot to clear the deck before sf v3 work begins; individual workstreams should land separately on top of this. Notable additions: - trace-collector.ts, traces.ts, src/tests/trace-export.test.ts — trace export plumbing - biome.json — Biome linter configuration - .gitignore — exclude native/npm/*/.node compiled binaries The bulk of the diff is across src/resources/extensions/sf/ (301 files) and src/resources/extensions/sf/tests/ (277 files), reflecting the ongoing sf extension work. Specific feature commits should follow this snapshot rather than being archaeology'd out of it. The 76MB native/npm/linux-x64-gnu/forge_engine.node compiled binary was left out of the commit — it's now gitignored and built locally. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> 2026-04-29 12:42:31 +02:00			`"id": "context7",`
			`"name": "Context7",`
			`"version": "1.0.0",`
			`"description": "Fetch up-to-date library documentation and code examples from Context7",`
			`"tier": "bundled",`
			`"requires": { "platform": ">=2.29.0" },`
			`"provides": {`
			`"tools": ["resolve_library", "get_library_docs"],`
			`"hooks": ["session_start", "session_shutdown"]`
			`}`
feat: add extension manifest + registry for user-managed enable/disable (#1238) Every extension gets a declarative extension-manifest.json (id, tier, provides, dependencies). A persistent registry at ~/.gsd/extensions/registry.json tracks enabled/disabled state. `gsd extensions` command family (list, enable, disable, info) lets users manage extensions without touching source code. Registry gate filters disabled extensions in loader.ts and resource-loader.ts before paths reach loadExtensions(). Zero breakage: extensions without manifests default to enabled, fresh installs have an empty registry. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> 2026-03-18 14:12:19 -06:00			`}`