Update cursor rules to document version-agnostic README standards

Rule updates:
- Add 'Available Tags' as required section in image READMEs (Quick Start)
- Remove 'Version Information' tables from required sections
- Document that root README should not have detailed tag documentation
- Update image README template with Available Tags section format
- Add guidelines for using version placeholders (<version>, <commit>)
- Emphasize version-agnostic approach throughout all rules

Changes in:
- documentation-standards.mdc: Added note about root README, updated required sections
- image-readme-standards.mdc: Added Available Tags to template, updated guidelines
- adding-new-images.mdc: Added Available Tags requirement, emphasized placeholders

Rationale:
- Tag information is image-specific, belongs in image READMEs
- Root README stays minimal and generic
- Version placeholders keep documentation accurate as versions change
- Consistent with recent README refactoring (commit 26ee08a)

Author: hacker-cb

.cursor/rules/adding-new-images.mdc

@@ -31,13 +31,15 @@ Create new directory: `images/<image-name>/` containing:
 Image README must include:
 - Overview and description
 - What's Inside (capabilities and tools, not specific versions)
-- Quick Start (pull, build, run)
+- Quick Start
+  - **Available Tags** section with tag types, examples, and recommendations
+  - Pull commands with tag examples (use `<version>`, `<commit>` placeholders)
 - Usage Examples
 - CI/CD Integration examples
 - Environment Variables
-- Building the Image
+- Building the Image (use `<version>` placeholders in build arg examples)
 
-**Important:** Do not hardcode specific version numbers in READMEs. Focus on capabilities and tools. See [Documentation Standards](documentation-standards.mdc) for version handling guidelines.
+**Important:** Do not hardcode specific version numbers in READMEs. Focus on capabilities and tools. Use placeholders like `<version>`, `<commit>` in all examples. See [Documentation Standards](documentation-standards.mdc) for version handling guidelines and [Image README Standards](image-readme-standards.mdc) for complete template.
 
 ## Update Root README
 

.cursor/rules/documentation-standards.mdc

@@ -15,9 +15,11 @@ Structure:
 2. Table of current images with links
 3. Generic quick start
 4. Project structure diagram
-5. Registry information
+5. Registry information (minimal, no detailed tag documentation)
 6. License
 
+**Note:** Detailed tag information belongs in individual image READMEs, not the root README.
+
 ## Image READMEs
 
 Must be:
@@ -30,8 +32,10 @@ Must be:
 
 Required sections:
 1. Overview
-2. What's Inside (capabilities and tools)
+2. What's Inside (capabilities and tools, no specific versions)
 3. Quick Start
+   - **Available Tags** - Tag types, examples, and recommendations
+   - Pull commands with tag examples
 4. Usage Examples (Docker commands, CI/CD integration)
 5. Environment Variables
 6. Building the Image
@@ -43,7 +47,7 @@ Sections to AVOID:
 - Feature explanations (framework features, not image features)
 - Troubleshooting (users can refer to upstream documentation)
 - Design Decisions (keep documentation focused on usage)
-- Version Information tables (versions change frequently)
+- Version Information tables (hardcoded versions change frequently)
 
 ## Version Handling
 

.cursor/rules/image-readme-standards.mdc

@@ -10,8 +10,10 @@ Image READMEs should focus on **how to use the Docker image**, not **how to deve
 
 **Required Sections:**
 1. **Overview** - What this image provides and its purpose
-2. **What's Inside** - Installed tools, versions, and components
+2. **What's Inside** - Installed tools and components (no specific versions)
 3. **Quick Start** - Pull, build, run commands using the image
+   - **Available Tags** - Tag types, examples, and usage recommendations
+   - Pull commands with examples for different tag types
 4. **Supported Chips/Platforms** - What the image supports
 5. **Usage Examples** - Docker commands showing image usage
    - CI/CD Integration (GitHub Actions, GitLab CI)
@@ -20,10 +22,9 @@ Image READMEs should focus on **how to use the Docker image**, not **how to deve
    - Image-specific configurations (e.g., ccache setup)
 6. **Environment Variables** - Variables set by the image
 7. **Building the Image** - How to build locally, build args
-8. **Version Information** - Component versions in the image
-9. **Additional Resources** - Links to framework documentation
-10. **License** - License information
-11. **Related Images** - Links to other project images
+8. **Additional Resources** - Links to framework documentation
+9. **License** - License information
+10. **Related Images** - Links to other project images
 
 **Optional Sections:**
 - **Notes** - Image-specific notes (e.g., excluded tools, limitations)
@@ -62,7 +63,7 @@ Image READMEs should focus on **how to use the Docker image**, not **how to deve
 ## Structure Template
 
 ```markdown
-# [Image Name] [Version]
+# [Image Name] Development Image
 
 Brief one-line description optimized for CI/CD and development.
 
@@ -73,12 +74,34 @@ What this image provides and its purpose.
 ## What's Inside
 
 **Component Category:**
-- Component 1 (version)
-- Component 2 (version)
+- Component 1 (no specific version)
+- Component 2 (no specific version)
 
 ## Quick Start
 
+### Available Tags
+
+| Tag Type | Example | Usage |
+|----------|---------|-------|
+| **Latest** | `latest` | Always points to newest build (floating) |
+| **Stable** | `stable` | Same as latest (semantic preference) |
+| **Version** | `<prefix>-v<version>` | Pin to specific version (recommended for CI/CD) |
+| **Commit** | `sha-<commit>` | Pin to exact git commit (debugging) |
+
+**Tag Recommendations:**
+- **Development**: Use `latest` for convenience
+- **CI/CD**: Use version tags (`<prefix>-v<version>`) for reproducibility
+- **Debugging**: Use commit tags (`sha-<commit>`) to reproduce exact build
+
 ### Pull Image
+```bash
+# Latest build
+docker pull ghcr.io/jethome-iot/jethome-dev-<image>:latest
+
+# Specific version (recommended for CI/CD)
+docker pull ghcr.io/jethome-iot/jethome-dev-<image>:<prefix>-v<version>
+```
+
 ### Build Your Project
 ### Interactive Development
 
@@ -105,12 +128,9 @@ Variables set by the image.
 
 ### Standard Build
 ### Custom Build Arguments
+Use `<version>` placeholders, not specific versions.
 ### Multi-Platform Support
 
-## Version Information
-
-Table of component versions.
-
 ## Notes
 
 Image-specific notes (optional).
@@ -185,7 +205,9 @@ void app_main(void) {
 2. **Link to Official Docs** - Provide links for framework-specific help
 3. **Keep It Concise** - Target ~250-350 lines for most images
 4. **Show Real Examples** - Use actual Docker commands, not pseudocode
-5. **Update Version Info** - Keep version table accurate
+5. **Use Version Placeholders** - Use `<version>`, `<commit>` instead of specific versions
+6. **Document Available Tags** - Every image README must have an "Available Tags" section in Quick Start
+7. **Version-Agnostic** - Describe capabilities, not specific version numbers (see documentation-standards.mdc)
 
 ## When Framework Content is Acceptable