feat(site): release portable snapshots and SEO audits in v0.2.0 - #11
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
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.
gkit can now capture public page facts into portable snapshot directories, audit them offline, and compare two observations without maintaining a site database. This releases the project-independent
sitecommand group in v0.2.0.Profiles supply site origins, routes, rules and repository identity. No Tripo configuration/data, scheduler, warehouse destination or project-specific CI orchestration is included. Existing argc v7.11.1 from main is retained.
Validation: 190 tests, 15 CLI scenarios, typecheck, 40 contract evaluation tasks, independent package installation, and a real Nuxt prerender/SSR fixture. The archive was inspected for project-specific material and repacked with identical SHA-256. The release workflow additionally checks the public installation's site schema.
Limits: no browser hydration/performance audit, historical CMS replay or served-revision attestation. Live Grok execution was tested with a fixture subprocess; no paid model call was made. Consumers own scheduling and long-term retention.