[compiler-threat-spec] docs: sync CTR-025 framework self-prompt misattribution spec - #53037
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Sync CTR-025 framework self-prompt misattribution spec
[compiler-threat-spec] docs: sync CTR-025 framework self-prompt misattribution spec
Aug 16, 2026
pelikhan
marked this pull request as ready for review
August 16, 2026 04:33
Contributor
There was a problem hiding this comment.
Pull request overview
Documents the existing CTR-025 framework prompt-stripping behavior and aligns its conformance mapping.
Changes:
- Adds CTR-025 and T-CTR-039 to specification version 1.0.23.
- Maps the rule to its implementation and tests.
- Adds compliance and release-note entries.
Show a summary per file
| File | Description |
|---|---|
specs/compiler-threat-detection-spec.md |
Adds the normative rule, mappings, test ID, and changelog. |
specs/compiler-threat-detection-compliance/README.md |
Maps CTR-025 to T-CTR-039. |
.changeset/sync-ctr-025-system-block-spec.md |
Records the documentation patch. |
Review details
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Suppressed comments (1)
specs/compiler-threat-detection-spec.md:423
- The changelog repeats the incorrect
v0.87.1minimum. Since the CTR-025 implementation is already present inv0.87.0, keep this entry aligned with the corrected sync-table version.
- Updated Section 2 spec-to-implementation sync table with version 1.0.23 mapped to minimum binary `v0.87.1` and no `.lock.yml` schema changes.
- Files reviewed: 3/3 changed files
- Comments generated: 1
- Review effort level: Balanced
|
|
||
| | Spec version | Minimum gh-aw binary version | Lock-file compatibility notes | | ||
| |--------------|------------------------------|-------------------------------| | ||
| | `1.0.23` | `v0.87.1` (or newer) | Adds normative coverage for framework self-prompt misattribution handling (CTR-025) in threat-detection setup by stripping only the leading framework-generated `<system>...</system>` block before analysis; no `.lock.yml` schema changes (runtime-only detection setup behavior). | |
Contributor
|
🎉 This pull request is included in a new release. Release: |
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.
This PR closes a spec/implementation drift: CTR-025 behavior (framework
<system>block stripping in threat-detection setup) was implemented and tested but not documented in the threat spec/compliance mapping.It updates the threat-detection specification and conformance map so the normative catalog, implementation mapping, and test IDs align.
Spec sync (v1.0.23)
specs/compiler-threat-detection-spec.mdto1.0.23.1.0.23→ minimum binaryv0.87.1, runtime-only behavior, no.lock.ymlschema change).1.0.23 (2026-08-16).Rule + mapping coverage
actions/setup/js/setup_threat_detection.cjs(stripFrameworkSystemBlock,SYSTEM_BLOCK_REMOVED_MARKER)actions/setup/js/setup_threat_detection.test.cjsConformance ID alignment
specs/compiler-threat-detection-compliance/README.mdwithCTR-025 → T-CTR-039.Release note entry
.changeset/sync-ctr-025-system-block-spec.md(patch) to record the documentation sync.