Implement EXT-9 idempotent knowledge publish and revoke with the upload index switch

Conversation 0 Commits 2 Files Changed 10

+289 -6

2 Commits

Author	SHA1	Message	Date
weichen	fbc924c240	Implement EXT-9 idempotent publish, prefix-enforced revoke, and the upload index switch ci / vet-and-test (pull_request) Successful in 41s Details Why: The red acceptance tests pin the EXT-9 semantics - held material must not enter retrieval until published, revoke must stop retrieval immediately and idempotently, manual sources must stay out of plugin reach. Evidence: TestKnowledgePublishIdempotentAndRevoke and TestUploadPreIndexSwitch green; go test ./... 32/32 packages ok; rows follow on the task card. Impact: hostcaps KnowledgePublish (per-ref row+vector cleanup then existing write path) and KnowledgeDelete (plugin:<id> prefix enforced); store DeleteKnowledgeBySource with vector cleanup; upload indexing gated by DisableUploadIndexing (default false = unchanged). Refs: EXT-9 proposal; red run at surface commit.	2026-10-08 15:55:02 +00:00
weichen	1ee32822c3	Add the EXT-9 publish/revoke surface and red acceptance tests Why: EXT-9 is the other step-4 hard prerequisite; the surface (Options.DisableUploadIndexing passthrough, Host.KnowledgePublish idempotent replace, Host.KnowledgeDelete prefix-enforced revoke, SurfaceVersion 2.2.0-experimental) must land with the acceptance reds pinned before implementation. Evidence: app red = publish not implemented; server red = switch-on still indexes (hits=1); rows recorded on the task card. Impact: pkg/extension additive surface (surface.txt updated); internal Options passthrough; Server.DisableUploadIndexing field; host method stubs. Behavior unchanged. Refs: EXT-9 proposal; task card.	2026-10-08 15:53:39 +00:00

Author

SHA1

Message

Date

weichen

fbc924c240

Implement EXT-9 idempotent publish, prefix-enforced revoke, and the upload index switch

ci / vet-and-test (pull_request) Successful in 41s

Details

Why: The red acceptance tests pin the EXT-9 semantics - held material must not enter retrieval until published, revoke must stop retrieval immediately and idempotently, manual sources must stay out of plugin reach.
Evidence: TestKnowledgePublishIdempotentAndRevoke and TestUploadPreIndexSwitch green; go test ./... 32/32 packages ok; rows follow on the task card.
Impact: hostcaps KnowledgePublish (per-ref row+vector cleanup then existing write path) and KnowledgeDelete (plugin:<id> prefix enforced); store DeleteKnowledgeBySource with vector cleanup; upload indexing gated by DisableUploadIndexing (default false = unchanged).
Refs: EXT-9 proposal; red run at surface commit.

2026-10-08 15:55:02 +00:00

weichen

1ee32822c3

Add the EXT-9 publish/revoke surface and red acceptance tests

Why: EXT-9 is the other step-4 hard prerequisite; the surface (Options.DisableUploadIndexing passthrough, Host.KnowledgePublish idempotent replace, Host.KnowledgeDelete prefix-enforced revoke, SurfaceVersion 2.2.0-experimental) must land with the acceptance reds pinned before implementation.
Evidence: app red = publish not implemented; server red = switch-on still indexes (hits=1); rows recorded on the task card.
Impact: pkg/extension additive surface (surface.txt updated); internal Options passthrough; Server.DisableUploadIndexing field; host method stubs. Behavior unchanged.
Refs: EXT-9 proposal; task card.

2026-10-08 15:53:39 +00:00

Implement EXT-9 idempotent knowledge publish and revoke with the upload index switch #106