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.
feat(figma): drift detection and mapping cache reuse (Phase E — T2F.10) #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: feat/figma-phase-d-cli
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
feat(figma): drift detection and mapping cache reuse (Phase E — T2F.10) #43
Changes from all commits
ab9e1c8f1582e38b8a7b7File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed these need coverage. Will add unit tests for LoadPreviousMeta, LoadMappings, and UpdateRunFigmaVersion in a follow-up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Acknowledged — this is a known limitation. LoadPreviousMeta currently matches by file key only, so running against a different node within the same file will incorrectly reuse stale mappings. Fixing this properly requires adding a node_id column to RunIndexEntry and updating the JSONL schema. Tracking as a follow-up for multi-node workflow support.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — the meta fetched for drift detection could be threaded into FetchFigma to avoid the redundant call. This requires changing FetchFigma's signature and plumbing the response through, so tracking as a follow-up to keep this PR focused on drift detection correctness.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is intentional. The drift check gates on Figma version only — it answers 'has the design changed?' If the Google Doc content changed, the user would simply re-run (the doc is always freshly fetched at the start of Execute). Coupling doc-change detection into the Figma drift path would conflate two independent concerns.