fix(artifact): prefer Agentic hook env vars#101
Merged
Conversation
1165b3a to
a264272
Compare
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.
Summary
AGENTIC_ARTIFACT_*env vars from artifact command hooks while relying on the central hook bridge for legacySPORES_*compatibility.artifact.writtenhook to use Agentic naming first.Dogfood Trail
This came from post-v0.5.0 dogfooding. The run produced a finalized design artifact for #16 and posted the design back to the issue:
#16 (comment)
It also exposed that artifact hook commands were still passing legacy
SPORES_ARTIFACT_*names despite the preferred Agentic hook contract.Follow-up roadmap:
Verification
bun testbun run typecheck