Release govoplan-docs v0.1.23: unify help discovery and batch semantic reads
Module Package Release / publish-packages (push) Successful in 12s
Module Package Release / publish-packages (push) Successful in 12s
This commit is contained in:
@@ -29,6 +29,21 @@ Semantic content is bounded plain text. Links must be local absolute paths or HT
|
||||
|
||||
Search indexes only published revisions and always requires provider reauthorization before returning a result. Generic public documentation generation reads static manifest topics only, so it cannot include tenant semantic entries. The separately authorized tenant export includes current entries and immutable history and sends `private, no-store`.
|
||||
|
||||
Collection/context projection and search authorization load required revisions
|
||||
in request-local batches of at most 400 identifiers. Read-only projection loads
|
||||
published content only, never pending draft bodies, and remains available if a
|
||||
pending draft reference is broken. Editors still receive an explicit error for
|
||||
an unavailable current revision. Revision tenant, entry, and publication-state
|
||||
references must agree before content is projected or indexed. An audience
|
||||
denial is checked before calling the subject provider; an allowed audience does
|
||||
not replace the provider's current permission checks.
|
||||
|
||||
This reduces Docs-owned database round trips without caching authorization
|
||||
between requests or importing subject-module internals. Owner-provider reads
|
||||
remain independent. The batch size is not a collection or export limit: complete
|
||||
semantic catalogues and separately authorized history exports can still require
|
||||
work proportional to their size.
|
||||
|
||||
## Backup, recovery, and module removal
|
||||
|
||||
Back up `docs_semantic_entries` and `docs_semantic_revisions` together with Core tenant and audit state. Restoring only one table breaks revision pointers and is unsupported. The installer blocks normal uninstall while rows remain. Destructive retirement is explicit, requires a database snapshot, and drops revision history before entries.
|
||||
|
||||
Reference in New Issue
Block a user