wiki-update

End-of-session vault maintenance is automated by creating or updating session logs, linking epics and stories in TaskNotes, promoting knowledge to compiled insights, and regenerating the vault index transactionally. This ensures metadata stays linked, discoverable, and up-to-date without manual cleanup.

Promoting session insights to compiled-insights pages is handled automatically during the vault update flow. The process extracts knowledge from the current session log, propagates updates to related architecture pages and TaskNotes, and ensures frontmatter-driven metadata cleanup before regenerating the index.

Yes, wiki-update is designed specifically for Ark vaults using TaskNotes. It requires this environment to execute its transactional flow, which links epics and stories, promotes knowledge, and regenerates the vault index atomically.

Linking epics and stories in TaskNotes is automated as part of the end-of-session wrap-up. The update process reads your session activity, updates the relevant TaskNotes to reflect progress, and ensures all metadata relationships are maintained before refreshing the vault index.

Vault index regeneration can fail or leave metadata inconsistent if performed manually without transactional safeguards. The wiki-update process applies a gating step tied to the index regen script, ensuring that frontmatter cleanup, knowledge promotion, and index updates are applied atomically to prevent partial failures.

A transactional vault update flow is needed at the end of any work session where new insights, TaskNotes progress, or epic and story updates must be persisted. Running it ensures your vault index reflects the latest state and that all knowledge links remain discoverable.