Skip to content

ref(source): 修正 Extension ownership 边界 - #82

Open
xiaoland wants to merge 3 commits into
mainfrom
feat/extension-ownership-correction
Open

ref(source): 修正 Extension ownership 边界#82
xiaoland wants to merge 3 commits into
mainfrom
feat/extension-ownership-correction

Conversation

@xiaoland

Copy link
Copy Markdown
Member

结果

  • 恢复仍在进行中的 knowledge-lifecycle-capabilities task packet,并将 GitHub unit 暂停在独立 owner correction 之后
  • 删除 core catalog 对 Extension Source schema 的 built-in ownership;Source class/runtime publication 成为唯一 authority
  • 将具体 Memos、RSS、Mail 契约明确留在 Spoke Unit TDD,并消费 Hub owner correction 3296867
  • 沉淀 promotion、dependency reuse 与 active-task cleanup guideline

验证

  • clean development database baseline:sources_types = []
  • 真实 SourceManager.sync_source_types() 发布 GitHub、Mail、RSS、Atom、Telegram、Twitter 后,六条 schema 与 Source class 精确一致
  • pdm run check:7 passed,40 skipped;Ruff、Pyrefly、migration integrity 通过
  • shared ref pre-bump / pre-commit checks 通过

交付边界

本 PR 只关闭跨 Extension ownership correction。GitHub-specific PyGithub、graph batch persistence 与 collection re-acceptance 继续留在暂停的 PR #80。Hub source correction 位于 InKCre/docs PR #18

- recover the active long-running packet removed during baseline cleanup
- integrate GitHub as a paused unit under the existing program
- isolate extension ownership correction as its own task
- publish source schemas only from registered Extension classes
- remove Extension profiles from core seed and readiness authority
- document durable owner, dependency, and active-task boundaries
- advance shared truth to Hub commit 3296867
- keep concrete Extension contracts in their owning Spokes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant