Draft changelog: secret redactor fixes and hook positioning#86
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
11 tasks
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
Adds this week's changelog entries covering the secret-redactor structural-output fix, the strict-mode exit-status fix, and clearer positioning for Forge's Claude Code hooks and guardrails.
Changes
FORGE_ENFORCE=1is set, and that guardrails are defence in depth (not a sandbox).FORGE_GUARD_STRICT=1exit status being propagated so theDEGRADEDsignal actually reaches Claude Code, with a note that PostToolUse can't block — blocking is the pre-action gate's job.Context
Source PR: #85 — CR-01 (structured-output redaction), CR-02 (strict-mode exit status), ME-24 (honest positioning).