Document current FluentAI architecture and retire obsolete Tk launcher - #2
Merged
Merged
Conversation
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.
FluentAI's design notes still described implemented features as future work, and its project contract required an obsolete Tk launcher even though the documented desktop app uses Electron. Replace the construction plans with concise current architecture, schema/privacy/curriculum/package decisions, limitations, and roadmap. Retain the original documents' Git provenance and design screenshots, correct the app output path, and remove the completed spaced-repetition roadmap item.
Remove the Tk launcher and update its file-existence assertion to cover Electron and the shared bridge. No learning-engine, learner-data, or screenshot changes.
Validation: 133 Python tests with no skips; 11 renderer scenarios; JS syntax/redaction checks; mocked smoke; Ruff; documentation links. Built and smoke-tested the PyInstaller bridge outside the checkout, packaged the macOS app using the lockfile-matching local Electron distribution, and passed ad-hoc signature verification plus packaged-bridge status. Build validation required Command Line Tools to avoid a broken host Xcode loader and a local Electron cache to avoid sandbox DNS. Physical-camera and clean-account GUI acceptance remain manual; no paid API calls were made.