Spell out explicitly, per run: check whether the shared index store already has a published index; if so, fetch it regardless of access level; a write-access user always continues to rebuild and publish back to that same store, and this is precisely what creates it there the first time the store is empty. A read-only user never rebuilds or publishes anything, whether or not the store already had content. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| cbk-quiz | ||
| ckb-export-okf | ||
| ckb-export-starlight | ||
| ckb-index-external | ||
| ckb-ingest | ||
| ckb-init | ||
| ckb-lint | ||
| ckb-onboard-me | ||
| ckb-project-summary | ||
| ckb-sync-changes | ||
| ckb-teach-me | ||
| ckb-upgrade | ||
| .gitadd | ||