Context
The live knowledge store has complete coverage for the 192 repositories visible to the current GitHub App installation, but GitHub metadata and the declared knowledge schema are inconsistent.
I corrected the current knowledge descriptions for these records:
KNOWLEDGE-115, 119, 120, 127, 128, 131, 141KNOWLEDGE-145, 146, 147, 148, 149, 152KNOWLEDGE-248 through 256
These fixes are vulnerable to being overwritten by the next GitHub sync until upstream repository metadata is corrected.
Upstream metadata work
Remove stale coming v0.4.x / under-construction metadata and update README status/install sections where applicable:
animus-protocolanimus-plugin-templateanimus-provider-claudeanimus-provider-codexanimus-provider-geminianimus-provider-oaianimus-provider-opencode
Add missing GitHub descriptions for:
animus-launchappanimus-mcp-githubanimus-chat-postgresanimus-config-yamlanimus-log-storage-s3animus-provider-codex-mcpanimus-config-postgresanimus-subject-postgresanimus-queue-postgresanimus-journal-postgresanimus-postgresanimus-environment-baseanimus-environment-dockeranimus-env-transportanimus-environment-railway
Recommended canonical descriptions are already present in the corresponding live knowledge records listed above.
Sync/schema work
The built-in knowledge kind declares only entity_kind and url, while synced records also contain repo_full_name, description, language, private, archived, default_branch, pushed_at, source, topics, metadata, and relationships.
Add these fields through a built-in-kind migration so validation and portal rendering match the actual payload. Do not redeclare the built-in kind.
GitHub App follow-up
- Pin
GITHUB_APP_INSTALLATION_ID if organization-wide code search is required.
- Install or authorize the App for the
animus-ecosystem organization, or ingest public plugin-registry entries separately, so external ecosystem repositories can appear in knowledge.
- Add consistent repository topics such as
animus, plugin, provider, subject-backend, workflow, and mcp.
Context
The live
knowledgestore has complete coverage for the 192 repositories visible to the current GitHub App installation, but GitHub metadata and the declared knowledge schema are inconsistent.I corrected the current knowledge descriptions for these records:
KNOWLEDGE-115,119,120,127,128,131,141KNOWLEDGE-145,146,147,148,149,152KNOWLEDGE-248through256These fixes are vulnerable to being overwritten by the next GitHub sync until upstream repository metadata is corrected.
Upstream metadata work
Remove stale
coming v0.4.x/ under-construction metadata and update README status/install sections where applicable:animus-protocolanimus-plugin-templateanimus-provider-claudeanimus-provider-codexanimus-provider-geminianimus-provider-oaianimus-provider-opencodeAdd missing GitHub descriptions for:
animus-launchappanimus-mcp-githubanimus-chat-postgresanimus-config-yamlanimus-log-storage-s3animus-provider-codex-mcpanimus-config-postgresanimus-subject-postgresanimus-queue-postgresanimus-journal-postgresanimus-postgresanimus-environment-baseanimus-environment-dockeranimus-env-transportanimus-environment-railwayRecommended canonical descriptions are already present in the corresponding live knowledge records listed above.
Sync/schema work
The built-in
knowledgekind declares onlyentity_kindandurl, while synced records also containrepo_full_name,description,language,private,archived,default_branch,pushed_at,source,topics,metadata, andrelationships.Add these fields through a built-in-kind migration so validation and portal rendering match the actual payload. Do not redeclare the built-in kind.
GitHub App follow-up
GITHUB_APP_INSTALLATION_IDif organization-wide code search is required.animus-ecosystemorganization, or ingest public plugin-registry entries separately, so external ecosystem repositories can appear in knowledge.animus,plugin,provider,subject-backend,workflow, andmcp.