Add wiki article drafts, session memory tools, reminders, and security updates #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "wiki-article-editor"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This branch adds the wiki article editor workflow, including article drafts, draft review, wiki link suggestions, and structured character visibility controls. It also improves session workflows with session memory search, proposed-session bot delivery, optional fourth reminders, and automatic reminders for party members who have not voted within three days of voting opening.
It also includes production-readiness fixes found during validation: restored session confirmation notifications, legacy import compatibility for older campaign exports, safer test database guards, updated dev auth/dev-server behavior, and dependency security patches across the backend, bot, and frontend.
Validation completed:
Backend tests: 284 passed
Bot tests: 135 passed
Frontend tests: 64 passed
Frontend build: passed
Backend, bot, and frontend dependency audits: clean
Dev server rebuilt and checked healthy before merge prep
GM-triggered "Rephrase with LLM" button on each article and bot proposal approval (for merge cases) now route through a new draft-review page where the GM can edit inline, send back to the LLM with comments for another iteration, approve, or discard before any LLM output replaces the article. Approve snapshots a LoreEntryVersion via the existing update_lore_entry path. Both the rephrase and merge prompts now explicitly require preservation of [[wiki-link]] and markdown formatting. - New lore_entry_drafts table (one draft per entry, unique constraint) - 6 new endpoints under /api/campaigns/{cid}/lore/{entry_id}/drafts - generate_lore_entry_draft Celery task with testable core - WikiDraftReview page (polling, autosave, iterate, approve, discard) - WikiProposals + CampaignDetail merge-style approvals route through the draft pipeline; new-entry proposals still approve directly - Legacy approve_lore_proposal merge branch retained as a direct-API fallback Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>