codeplay-common 4.2.4 → 4.2.5

package/agent-templates/v1.0/AGENTS/playstore-media.md

@@ -1,17 +1,17 @@
-# Play Store Media Assets Rule
-
-- Screenshots and videos generated for Play Store submission must be stored only under the `Playstore/` directory at the repository root.
-- Organize assets into explicit subfolders and never place them beside app source or temp files.
-- Use this naming structure:
-
-  - `Playstore/Screenshots/<platform>/<orientation>/<app-version>/`
-  - `Playstore/Videos/<platform>/<type>/`
-
-Where:
-
-- `<platform>` examples: `android`, `phone`, `tablet`
-- `<orientation>` examples: `portrait`, `landscape`
-- `<type>` examples: `feature`, `promo`, `trailer`
-- `<app-version>` is the release/build identifier (for example `v1.2.3`).
-
-- File names should include device and resolution when useful (for example `google-pixel-8-portrait.png`, `galaxy-tab-landscape.mp4`).
+# Play Store Media Assets Rule
+
+- Screenshots and videos generated for Play Store submission must be stored only under the `Playstore/` directory at the repository root.
+- Organize assets into explicit subfolders and never place them beside app source or temp files.
+- Use this naming structure:
+
+  - `Playstore/Screenshots/<platform>/<orientation>/<app-version>/`
+  - `Playstore/Videos/<platform>/<type>/`
+
+Where:
+
+- `<platform>` examples: `android`, `phone`, `tablet`
+- `<orientation>` examples: `portrait`, `landscape`
+- `<type>` examples: `feature`, `promo`, `trailer`
+- `<app-version>` is the release/build identifier (for example `v1.2.3`).
+
+- File names should include device and resolution when useful (for example `google-pixel-8-portrait.png`, `galaxy-tab-landscape.mp4`).

package/agent-templates/v1.0/AGENTS/versioning.md

@@ -1,14 +1,14 @@
-# Versioning and Release Notes Rule
-
-- Any change to app version fields (version code and/or version name) must be followed by update of tracked release documentation.
-- Record every version bump in both files:
-  - `CHANGELOG.md` (full technical history)
-  - `RELEASE_NOTES.md` (public-facing release notes)
-- Each update entry must include, at minimum:
-  - Date (`YYYY-MM-DD`)
-  - New version name
-  - New version code (or build number)
-  - Files changed for the version bump
-  - 3–8 bullet points of user-impacting changes
-- If `CHANGELOG.md` or `RELEASE_NOTES.md` do not exist, create them in the repo root.
-- Keep these files under version control (do not place in `.gitignore` paths or `agent-temp/`) so they sync across systems.
+# Versioning and Release Notes Rule
+
+- Any change to app version fields (version code and/or version name) must be followed by update of tracked release documentation.
+- Record every version bump in both files:
+  - `CHANGELOG.md` (full technical history)
+  - `RELEASE_NOTES.md` (public-facing release notes)
+- Each update entry must include, at minimum:
+  - Date (`YYYY-MM-DD`)
+  - New version name
+  - New version code (or build number)
+  - Files changed for the version bump
+  - 3–8 bullet points of user-impacting changes
+- If `CHANGELOG.md` or `RELEASE_NOTES.md` do not exist, create them in the repo root.
+- Keep these files under version control (do not place in `.gitignore` paths or `agent-temp/`) so they sync across systems.

package/agent-templates/v1.0/AGENTS.md

@@ -1,6 +1,6 @@
 # Project Instructions
-# Version 1.0
+# Version 1.1
 
-- `AGENTS/agents.md`
-
-Read and follow that file before modifying the project.
+- `AGENTS/agents.md`
+
+Read and follow that file before modifying the project.