Repository navigation
FreeOS blue chrome, GitHub-only updates, Organization OS - #13
Merged
Merged
Conversation
Stop PyPI/Tencent Octop update feeds so 0.0.1 no longer looks stale, stage FreeOS portable zips from XYAIStudio/FreeOS releases, migrate leftover Octop rose chrome to brand blue, and add a dual-loop Organization OS page wired to the local sidecar and org APIs. Co-authored-by: XYAI Labs <haoboy8@gmail.com>
Return a dict from sidecar start for mypy, drop unused venv monkeypatches, and sort self-update test imports. Co-authored-by: XYAI Labs <haoboy8@gmail.com>
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
2 participants
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.
Summary
Fixes three product issues on FreeOS
0.0.1without bumping the version.A — Chrome still felt red. Installed leftovers kept Octop
rose(#E85D75) inlocalStorage. Source default was already XYAI blue#0033FF, but boot never migrated the old palette. First launch now migrates leftoverroseonce (users can still pick it later),index.htmlboots withdata-palette="freeos", and tests fail if the default primary is Octop-red.B — Update channel tracked Octop and could brick the app. Checks went to PyPI
octop/ Tencent COS mirrors. Upstream Octop is0.9.x/1.0.0, so FreeOS0.0.1always looked stale; applying the update installed Octop and broke launch. FreeOS now checks onlyhttps://github.com/XYAIStudio/FreeOS/releases. “Update available” only when a newer FreeOS desktop/portable asset exists. Apply stagespending-portable.zip; the desktop shell extracts it on next launch and keepsFREEOS_STAMP. Settings copy says GitHub / FreeOS, never an Octop update server.C — Organization OS is first-class. Nav is 组织 OS. The page is a live dual-loop: FreeOS data plane (employees / skills / MCP / tasks) ↔ openXYOS control plane (modules / governance / health), with real counts. One-click: assemble employees from blueprints, pack skills/MCP back, run
org loopand show the real timeline. Sidecar down shows a start/recover action instead of a blank page.Product version stays 0.0.1. Same-version GitHub
v0.0.1will not prompt an in-app update (by design). New Windows installers should be attached to Releasev0.0.1when Desktop Package CI finishes.Target branch
mainType of change
Test plan
uv run pyteston update/org/github-release tests (130 passed) +mypy --strict src/octop+ dashboard theme vitest (32 passed) +npx tsc --noEmitmake all/ GitHub CIChecklist
CHANGELOG.mdVerify (no code)
github.com/XYAIStudio/FreeOS. On0.0.1with latest GitHub release alsov0.0.1, no “new version” prompt. Do not hitpypi.orgorfinnie-1258344699.Release
Keep tag
v0.0.1. After Desktop Package workflow producesFreeOS-desktop-windows-amd64-0.0.1.exeandFreeOS-desktop-windows-arm64-0.0.1.exe, attach them to https://github.com/XYAIStudio/FreeOS/releases/tag/v0.0.1. Uninstall the old build if a previous update already replaced it with Octop.