@iamdevlinph/codex-kit 1.0.19 → 1.0.21

package/LICENSE

@@ -1,6 +1,3 @@
-This license applies only to files included in the published
-@iamdevlinph/codex-kit npm package. It does not apply to repository-only files.
-
 ISC License
 
 Copyright (c) 2026 Devlin Pajaron

package/README.md

@@ -246,9 +246,13 @@ standard-library modules.
 
 ## License
 
-Files included in the published `@iamdevlinph/codex-kit` npm package are
-licensed under the [ISC License](LICENSE). Repository-only files remain
-proprietary and are not covered by that license.
+This repository and the published `@iamdevlinph/codex-kit` package are licensed
+under the [ISC License](LICENSE).
+
+## Security
+
+See [SECURITY.md](SECURITY.md) for supported versions and private vulnerability
+reporting instructions.
 
 ## References
 

package/assets/TEMPLATE_AGENTS.md

@@ -121,12 +121,16 @@ conditional procedures into validated project skills.
 
 ## Structure
 
-- Follow the repository's organization and naming. Prefer focused files and
-  split mixed responsibilities when readability improves.
+- Follow the repository's organization and naming. Organize feature-specific
+  code under the feature's existing directory; when a feature contains multiple
+  substantial UI pieces, place them in a `<feature>/components` subdirectory.
+  Keep broadly reused code in the repository's established shared locations.
 - Keep route and page files focused on page-level composition, data loading, and
   orchestration. Extract substantial self-contained UI sections and complex
-  page-specific logic into colocated feature components or modules. Keep small
-  one-use markup inline; do not create components solely to reduce line count.
+  page-specific logic into focused files colocated with the feature. Split large
+  or mixed-responsibility files by cohesive behavior so each file remains easy
+  to read, navigate, test, and review. Keep small one-use markup or logic inline;
+  do not create files or components solely to reduce line count.
 - Use intent-revealing domain names. A reader should understand what a variable
   contains or what a helper guarantees at the call site without opening its
   implementation. Avoid vague transformation names such as `normalized`,

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@iamdevlinph/codex-kit",
-	"version": "1.0.19",
+	"version": "1.0.21",
 	"description": "Portable Codex subagents and project AGENTS.md defaults.",
 	"type": "module",
 	"bin": {