Skip to content

feat(packaging): add Antigravity CLI plugin artifact - #96

Merged
phodal merged 3 commits into
QoderAI:mainfrom
aaaazqh:feat/antigravity-plugin-artifact
Aug 21, 2026
Merged

feat(packaging): add Antigravity CLI plugin artifact#96
phodal merged 3 commits into
QoderAI:mainfrom
aaaazqh:feat/antigravity-plugin-artifact

Conversation

@aaaazqh

@aaaazqh aaaazqh commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a deterministic, fail-closed builder and verifier for a static Antigravity CLI plugin artifact containing the canonical Better Harness Skill and its validated dependency closure.

Why

  • Issue/Story: Refs [Feature]: Add support and adapter for Agy CLI #67
  • User or maintainer outcome: contributors can build and verify an Agy CLI-compatible plugin bundle without claiming native installation, discovery, invocation, or broader host support.

Traceability and Scope

  • Spec/ADR, if applicable: docs/specs/2026-08-19-67-antigravity-plugin-artifact.md
  • Acceptance criteria addressed: AC-1 through AC-12
  • Canonical owners changed: Antigravity-specific source manifest, artifact builder/verifier, focused artifact tests, and four source-document link targets needed by the canonical dependency closure
  • Explicit non-goals: native agy install/list/invocation/uninstall smoke; session evidence; host-support catalog or adapter-matrix claims; README Quickstart; authentication, network access, or automatic installation

Change Type

  • Feature
  • Bug fix
  • Tests only
  • Documentation/community
  • Refactor with no intended behavior change
  • Dependency, packaging, or infrastructure

Test and Review Evidence

Check Result
Antigravity artifact + existing Codex artifact + doc-link suites 49 passed, 0 failed, 3 Windows capability skips
Real artifact build -> verify -> Better Harness CLI help -> atomic replace -> verify Passed; 627 files / 739 entries; no staging or backup residue
npm run pack:verify with task-local npm cache Passed; npm package 546 entries, runtime archive 575 entries
npm test 1,420 passed, 7 environment failures, 21 skipped; six failures are Windows symlink EPERM, one is the isolated worktree lacking its own Vitest file
Doc links, generated graph parity, syntax, whitespace, privacy scan Passed; doc-link 6/6 and generated graph content unchanged

Manual or visual evidence: separate planning, execution, and review agents audited the official Agy CLI v1.1.14 manifest contract, recursive Markdown/ESM closure, portable path identity, atomic publication/rollback, concurrent destination replacement, and failure-state observability. Final review found no remaining P0-P3 issues.

Risk and Recovery

  • Compatibility and cross-platform impact: the artifact contract models Windows, macOS, and Linux path rules; three special-file/symlink tests were skipped because this Windows environment could not construct those fixtures.
  • Package, plugin, schema, or generated-file impact: adds an Antigravity-only static artifact path; it does not register Antigravity as a supported host or change root package metadata.
  • Rollback or recovery path: revert this commit to remove the source manifest, builder, verifier, tests, spec, and link-integrity corrections.
  • Residual risk or unverified boundary: no native agy install, discovery, invocation, listing, or uninstall smoke was available. This PR proves only a buildable and verifiable static artifact slice.

AI Involvement

  • Level: Generated with AI assistance
  • Human review and validation: the contributor approved the issue scope and submission. Implementation and evidence were independently checked through separate planning, execution, and review agents; upstream maintainer review is requested.

Checklist

  • I followed AGENTS.md, CONTRIBUTING.md, and the relevant canonical-owner guidance.
  • The change is focused and does not include unrelated local or generated state.
  • Tests and documentation match the behavior actually delivered.
  • Markdown links were checked when documentation moved or changed.
  • Cross-platform behavior was considered for Windows, macOS, and Linux.
  • Package/runtime verification was run when shipped files or dependencies changed.
  • User-facing or compatibility changes are recorded in CHANGELOG.md (intentionally omitted: this issue-scoped slice adds no support claim).
  • I have the right to contribute this work under the repository's MIT License.

Co-authored-by: Codex (GPT 5.6 Sol) codex@openai.com
@phodal

phodal commented Aug 20, 2026

Copy link
Copy Markdown
Member

hi @aaaazqh make sure GitHub Action passed, no failing check/

aaaazqh and others added 2 commits August 21, 2026 21:41
The three reference links this branch repairs were broken in the repository
already. They survived because `classify` cannot tell a slash-free
`custom-agents-review.md`, a real sibling one directory up, from `AGENTS.md`,
a file convention in a repository under analysis, so it treats every slash-free
token as conceptual and checks neither. Check slash-free targets written as link
syntax, excluding the convention names, so the repair cannot silently regress.

`docs/adapters/contributing-new-coding-agent.md` cites `.agents/` and `.github/`
as repository URLs because the artifact allowlist excludes both. That keeps the
link working inside the artifact but gives up the guarantee a relative link had:
the doc-link graph no longer notices when the target moves. Check that
repository URLs at a mutable ref still resolve, which covers 44 such links
across the site tree and this doc rather than only the two here.

Name the offending entry when the builder or verifier rejects a path. A
dependency release that starts shipping a `dist/` directory fails the build, and
`Source path is outside the artifact allowlist` alone leaves no way to tell
which of 739 entries caused it. Details carry repository-relative paths only,
so errors still cannot leak the operator's filesystem layout.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@phodal
phodal merged commit a905242 into QoderAI:main Aug 21, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants