Repository navigation
feat: portable UI issue export and offline source inspection - #86
Merged
Merged
Conversation
|
View your CI Pipeline Execution ↗ for commit d5881ba
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
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.
UI annotations require manual JSON/path rewriting to hand off to another checkout. This adds
domscribe issue exportfor one selected annotation and offlineissue inspect, preserving explicit expected/observed behavior, setup steps and project-relative source anchors. Inspection reports matched/changed/missing/unverified/unsafe and renders JSON or fenced Markdown. Runtime/replay are opt-in; bounded validation, privacy filtering and source containment prevent stale selectors or sanitized identities being treated as actionable.Fresh React testing exposed that fileHash described React Refresh output. Vite now records a separate exact original-source hash; old/unconfirmed hashes stay unverified. Metadata upgrades persist without duplicate index counts.
Validation: uncached configured full lint/test/build/typecheck passed (2,223 tests), followed by all 180 manifest tests and affected checks after two further regressions. Emitted dependency scan passed 497 files. Fresh packed React18/npm/Vite7 and Vue3/pnpm/Vite8 native browser flows passed capture/export, stopped reporter session, untouched packet inspection in a fresh source worktree, changed-source negative, wrong-business refusal, production stripping and zero app errors. The permanent --issue-handoff harness also passed exact React/npm/Vite7 and Vue/pnpm/Vite5 raw-runtime CI configurations (12/14 groups) and now runs in those existing CI rows. pnpm uses explicit local-tarball overrides. A historical native Hoppscotch annotation exported unchanged, preserved context_required and correctly inspected as unverified. Independent review findings were reproduced RED, fixed and re-reviewed; permanent harness reviewed too.
Usage and evidence: docs/portable-issue-handoff.md and docs/portable-issue-handoff-verification.md. New commands are source/local-build only, absent from npm 0.7.0. New Next/Nuxt CLI paths and real repair benefit remain unqualified. No publishing, deployment, demand or agent-superiority claim.