Repository navigation
Stage D part 2: Data Lifecycle and Chat groups - #1310
Merged
Paul Lizer (paullizer) merged 1 commit intoAug 19, 2026
Merged
Conversation
Move cards across panes so they sit with the settings they actually
work with, without touching a single field name.
Data Lifecycle (new group)
Retention retention-policy-section from workspaces
Classification document-classification-section from workspaces
Archiving conversation-archiving-section from safety
These three decide how long content lives and how it is labelled.
Archiving was under Safety, which describes what it guards against
rather than what it does.
Chat (new group)
Chat Experience processing-thoughts-section from ai-models
chat-file-uploads-section from workspaces
(carries nested conversation-contents-drawer-section)
workspace-scope-lock-section from workspaces
Feedback & Alerts user-feedback-section from safety
desktop-notifications-section from safety
Moves use move_card.py, which refuses to write unless every source line
lands in exactly one output. Nested cards travel with their parent and
the gap after a card travels with it, so interleaved modals stay with
the tab owning their trigger.
Navigation is now 13 groups / 27 tabs / 88 sections.
Verified
field contract 462 names / 110 card ids, unchanged
regression set 32 failures, identical to baseline
jinja compile 29/29 admin templates
xss sinks 5 changed files pass
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Paul Lizer (paullizer)
merged commit Aug 19, 2026
87ad47f
into
feature/admin-settings-ia
11 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second batch of Stage D. Creates the Data Lifecycle and Chat groups by moving cards across panes.
Base:
feature/admin-settings-ia.Why these two groups
Data Lifecycle. Retention policy, document classification and conversation archiving all answer the same question — how long does content live and how is it labelled — but they were split across Workspaces and Safety. Archiving in particular sat under Safety, which describes what it protects against rather than what it does.
Chat. Settings that shape what a conversation looks and behaves like were scattered across AI Models, Workspaces and Safety. Feedback and desktop notifications are about how the app talks back to the user, not about safety enforcement.
What moved
retention-policy-sectiondocument-classification-sectionconversation-archiving-sectionprocessing-thoughts-sectionchat-file-uploads-sectionworkspace-scope-lock-sectionuser-feedback-sectiondesktop-notifications-sectionconversation-contents-drawer-sectionis nested insidechat-file-uploads-sectionand travelled with it without being named.Navigation is now 13 groups / 27 tabs / 88 sections.
How the moves were done safely
move_card.pyworks line by line and refuses to write unless every source line lands in exactly one output. Two behaviours matter:No settings changed
Not one
name=attribute was touched, so the form posts exactly the payload it did before and every saved value survives.Next
Remaining Stage D groups: Appearance, AI Models, Agents & Actions, Workspaces, Workflow, Knowledge, Security, Operations, Help. Backup & Recovery goes last because its ~985-line migration workflow has to split as one unit.