base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct integration attribution dependency scopes

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-11 13:10:18 +00:00
parent 5aac2a0ee1
commit bb2528532b
3 changed files with 17 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/roadmap/remediation.md
View File

@@ -281,7 +281,14 @@ the affected existing suites. Public behavior and exports remain unchanged.
## R7: Correct the scope descriptions in module-local attribution
**Status:** Open. **Priority:** P3.
**Status:** Completed (2026-10-11). **Priority:** P3.
**Completed work:** ConfigKit is identified as a direct ckprompt dependency.
Both integration notices now identify copied policy entries as core-dependency
material with repository-root paths. Checked the direct import/requirement and
the material's actual locations. Local license links pass; all other copyright,
license, notice, and pinned source wording is preserved. Grants and verbatim
license files are byte-for-byte unchanged, and whitespace checks pass.
**Evidence:** [ckprompt attribution](../../integrations/ckprompt/docs/oss/attribution.md)
labels ConfigKit as a transitive dependency, but