Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Bump next and eslint-config-next 16.3.3 -> 16.4.2 (RCE, SSRF, cache poisoning advisories affecting <=16.3.7) - Pin sharp override 0.35.4 -> 0.35.5 (libheif/librsvg advisories) - Override source-map-js to 1.2.2 (indexed source-map DoS) - Rewrite useIsMobile with useSyncExternalStore to satisfy the react-hooks/set-state-in-effect rule in the new eslint-config-next Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KKzPb9c4k6xHyHPWC61n1x
…, symlinks
The engine wrappers detected direct execution with
`import.meta.url === \`file://${process.argv[1]}\``, which never matches
when the path is percent-encoded (spaces, non-ASCII), on Windows drive
paths, or through a symlink, so `node engine/memory.mjs ...` exited 0
without doing anything. Add a shared realpath + pathToFileURL helper
(the same approach the Antigravity build/check scripts use) and cover it
with a regression test that runs the entrypoints from such a path.
Also align @next/mdx with next 16.4.2 and correct the [Unreleased]
security entry, which still named Next.js 16.3.3 and sharp 0.35.4.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KKzPb9c4k6xHyHPWC61n1x
This branch had an error being 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
This PR turns AG Kit v2 into a genuinely runtime-neutral operating layer.
shared/is canonical,runtimes/<runtime>/owns host-specific behavior, and generated host trees are projections rather than competing sources of truth.The architectural goal is IJFW-class multi-runtime discipline and useful feature-class parity through AG Kit's own implementation — not source-code duplication and not a single-runtime fork.
Core architecture
ag-core)scout,architect,builder,reviewershared/packs/runtimes/<runtime>/.agents/,.claude/,.gemini/, managed instruction files, and plugin folders are projectionsRuntime-neutrality cleanup
This branch removes the old assumption that AG Kit == Antigravity Kit while retaining Antigravity as a supported first-class adapter.
Removed/moved old repository-wide Antigravity source/tooling assumptions, including:
.agents/antigravity.json.agents/.github/workflows/antigravity.ymlscripts/check-platform-drift.mjsAntigravity-specific source now lives under
runtimes/antigravity/; only the host projection belongs under.agents/.The root runtime contract now rejects:
primary_runtime/primaryRuntimedeclarations;.agents/;platform-capabilities.jsonand adapter contracts;16 runtime targets
First-class: Antigravity, Claude, Codex, Gemini, Qwen, Kimi, Cline.
Connected: Cursor, Windsurf, GitHub Copilot.
Bridge: OpenCode, OpenClaw, Aider, Wayland, Hermes, Pi.
Capabilities are declared in
platform-capabilities.json; AG Kit does not claim native surfaces that an adapter cannot independently verify.Runtime lifecycle
ag-kit runtime detectag-kit runtime install-presentruntime install / doctor / uninstalllive / standing-by / degraded / untouched.ag-kit/memory/v<CLI_VERSION>;--branchis an explicit dev/ref overridePackaged lifecycle smoke
The Linux CLI job installs the real npm tarball and exercises multiple ownership/projection shapes:
init → update → status, preserving a user-owned file;install → doctor(live) → uninstall → doctor(untouched);install → doctor(live) → uninstall → doctor(untouched);install → doctor(live) → uninstall → doctor(untouched).Each runtime smoke verifies ownership metadata, restoration/preservation of pre-existing user state, and persistence of project memory.
Runtime artifacts
build:runtime-artifactsis adapter-neutral. It discovers adapters that expose a real native artifact builder, validates each returned runtime/output, and emits a genericdist/runtime-artifacts/ARTIFACTS.jsoninventory.No root workflow hard-codes Antigravity artifact paths. If only one runtime currently has a native package/plugin artifact, that remains an adapter capability rather than a product-wide assumption.
Engine parity
DESIGN.mdcontract with 12 templates and validationAdapter-specific native features
Richer host-native features stay behind their adapter boundary.
Examples:
AGENTS.md, shared skills, and plugin/MCP surfaces;A richer adapter does not become the product's primary runtime.
Security / integrity
$HOMEautomaticallyDocumentation cleanup
Updated to the v2 runtime-neutral model:
README.md/README-VI.mdAGENTS.md/CLAUDE.mdAGENT_FLOW.mdMIGRATION.mdSECURITY.mdPRODUCTION_CHECKLIST.md.github/RELEASE_SETUP.mddocs/ARCHITECTURE_V2.mddocs/RUNTIMES.mddocs/PARITY_IJFW.mdcli/README.mdweb/README.mdHistorical Antigravity references remain only where they describe migration history or the Antigravity adapter itself.
IJFW parity posture
“Like IJFW” here means matching useful feature classes and multi-runtime operational discipline while preserving AG Kit's own code, names, lifecycle model, capability matrix, and privacy posture.
Intentional differences include:
Validation
Current head validation is rerunning after the final documentation inventory fix. The PR remains Draft until the final head has complete repository evidence.
No version bump, release tag, npm publish, merge, or production deployment is performed by this refactor checkpoint.