haeaeae/silo-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: use canonical plugin repository names (#359)

Browse Source
This commit is contained in:
Quick
2026-07-09 20:13:33 -04:00
committed by GitHub
parent 648e5c76ef
commit 98a22dafd2
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+3 -2
View File
@@ -40,7 +40,8 @@ Do not assume all plugin-related code lives in this repo.
- `silo-plugin-sdk` owns the public plugin SDK, protobuf contracts, generated plugin API code, manifest helpers, and runtime bootstrap.
- `silo-plugins` owns the central plugin catalog / repository manifest.
- First-party plugins such as `silo-plugin-tmdb`, and `silo-plugin-tvdb` live in their own repositories.
- First-party plugins such as `silo-plugin-metadata-tmdb` and
`silo-plugin-metadata-tvdb` live in their own repositories.
- `Silo` owns host-side plugin installation, runtime management, API handlers, and integration logic.
When a task mentions plugins, first determine whether the change belongs in this repo, the SDK repo, the catalog repo, or a specific plugin repo. Prefer coordinated multi-repo changes over forcing plugin work into `Silo`.
@@ -99,4 +100,4 @@ Recent history follows Conventional Commit-style subjects such as `feat(playback
**PR requirements.**
- Link the capability epic or sub-issue the PR serves (`Part of #NNN`). PRs with no linked scope item will be questioned at review.
- One concern per PR; Conventional Commit subject; AI-use disclosure in the PR body.
- One concern per PR; Conventional Commit subject; AI-use disclosure in the PR body.