Repository navigation
Skopeo - #149
Open
LakshmanTurlapati wants to merge 7 commits into
Open
Skopeo#149LakshmanTurlapati wants to merge 7 commits into
LakshmanTurlapati wants to merge 7 commits into
Conversation
Complete the automated Skopeo milestone and retain explicit human/live evidence boundaries.
Set the extension, showcase, skill, docs, and store metadata to 1.0.0 and advance fsb-mcp-server to 1.0.0. The legacy showcase dashboard version is now kept in sync by sync-product-version, and the concierge footer reads APP_VERSION instead of a hardcoded string.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Bring in main's extension 0.9.92 and fsb-mcp-server 0.11.1 work while keeping Skopeo's 1.0.0 version alignment. - Version surfaces stay at 1.0.0; every non-version change from main is kept. - CHANGELOG.md and mcp/CHANGELOG.md list 1.0.0 (now dated 2026-10-13) above main's 0.9.92 and 0.11.1 entries. - mcp/README.md gets its own 1.0.0 section above main's 0.11.1 and 0.11.0 sections, so only the current release carries the Compatibility line. - npm test runs both sides' additions; the lattice bridge smoke test counts 371 importScripts mentions and 365 call sites and keeps both sides' load-order checks; the lifecycle smoke test uses main's isolated HOME. - The release-notes page opens on the newest documented release instead of showing 1.0.0 as an archived release with no notes. - messages*.xlf line references follow the concierge component's new lines.
Bring in MCP 0.11.2 (#152): the dark-logo server icon, the packaged assets/ directory, and automatic npm publishing on merge to main. Version conflicts resolve to the branch's 1.0.0 alignment. server.json keeps 1.0.0 and gains the registry icon. The MCP changelog and README list 1.0.0 above 0.11.2, and their 1.0.0 release notes now describe the automatic publish that merging into main triggers.
Bring in the showcase design refresh (#151): the agent-connection homepage, localized marketing metadata, full support answers, the DB-IP credit, and video sitemap validation. The llms sources and generated files take main's refreshed copy with the branch's 1.0.0 release versions. The concierge footer drops the personal credit as main does and keeps the APP_VERSION binding instead of main's hardcoded 0.9.90.
4 tasks done
Bring in the Online-Mind2Web benchmark lead for the showcase and README (#163) and the Glama maintainer manifest (#154). The root test chain keeps the branch's Skopeo suites and adds main's benchmark asset parity suite. The llms-full source and generated file take main's benchmark copy with the branch's 1.0.0 release versions.
This branch has not been deployed
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
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
bc64a63e): adaptive HUD lifecycle shell, drive context router with semantic anchors, Skopeo HUDs generalized across the capability catalog, permission-scoped drive corpus boundary, Chrome-local graph foundation, governing lineage/evidence deadline engine, folder-reading HUD, cited-ask decision policy, and current-user alerts with release hardening. Includes the milestone planning archive under.planning/milestones/v1.2.0-SKOPEO-phases/.ba7bd43a): extension, showcase, skill, docs, and store metadata move to1.0.0;fsb-mcp-serveradvances to1.0.0.sync-product-versionnow also managesshowcase/dashboard.html, and the concierge footer readsAPP_VERSIONinstead of a hardcoded version.Merge with main
main(extension 0.9.92 / MCP 0.11.1) is merged in (692c6814). Versions stay at 1.0.0. The 1.0.0 changelog and MCP README entries sit above main's 0.9.92 / 0.11.1 entries.mainopens on the newest documented release, so 1.0.0 isn't shown as an archived release with no notes. Adding real 1.0.0 notes to that page is still open.tests/skopeo-browser-contract.test.js(also run bytest:skopeo-ask-evals/test:skopeo-release-evals) fails locally with headless Chrome 155: "Chrome dump contains the escaped Skopeo result node". It fails the same way before the merge.Verification
node scripts/sync-product-version.mjs --check→extension 1.0.0; MCP 1.0.0node tests/version-sync.test.js→ PASSnpm run validate:extension,npm run test:mcp-smoke, and the showcase CI steps (i18n gates, component tests, extract-i18n no-diff, build, hreflang, bundle budgets) pass locally.npm testpasses apart from the Chrome-dependent Skopeo browser contract noted above.