Skip to content

fix: scope forge drift verify to a deployed target manifest#74

Merged
N4M3Z merged 1 commit into
mainfrom
issue-61
Jul 8, 2026
Merged

fix: scope forge drift verify to a deployed target manifest#74
N4M3Z merged 1 commit into
mainfrom
issue-61

Conversation

@N4M3Z

@N4M3Z N4M3Z commented Jul 8, 2026

Copy link
Copy Markdown
Owner

Closes #61

Problem

forge drift cannot verify a build against the target it was deployed to; verification scans the whole target instead of the deployed manifest's scope.

Fix

Scope drift verification to the deployed target manifest (new drift/scope module with tests).

Test plan

  • cargo test (drift_target integration tests)
  • CI build matrix

forge drift could not verify a module's build against where it deployed:
the positional form was rejected and --upstream against a multi-module
tree (~/.claude) reported every other module's file as 'upstream only'.
Add forge drift --target <BASE> that walks build/<provider> and compares
each file to <BASE>/<provider-target>, scoped to this module — files
built-but-not-deployed surface as local-only, and this module's deployed
files (per the target .manifest + provenance attribution) that are no
longer built surface as drift. Mutually exclusive with --upstream.
@N4M3Z N4M3Z merged commit ab6c418 into main Jul 8, 2026
4 checks passed
@N4M3Z N4M3Z deleted the issue-61 branch July 8, 2026 23:08
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.

forge drift can't verify a build against its deployed target

1 participant