Skip to content

Generate changelog provenance from committed skill bytes #480

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

Release notes can claim an upstream revision from an uncommitted working file even though the changed skill inventory belongs to a committed head.

Proposal

Read surviving skill provenance from regular committed blobs, using the same revision as the change observation.

Acceptance criteria

Altered, missing and linked working copies cannot substitute provenance; removed skills retain their committed prior provenance and invalid committed metadata refuses the batch.

Reproduced offline against freshly fetched main using synthetic fixtures. No inspected source was executed and no provider experiment was launched. Size: S.

Part of #101.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions