Rename `latest` flow to `staging` for better CI/CD semantics

## 🎯 Problem Statement

The current `latest-{sha}` flow naming is semantically confusing in modern CI/CD pipelines. When code is pushed to the main branch, it generates images tagged as `latest-{sha}`, but these are **not** production-ready "latest" releases—they're pre-production staging images awaiting validation before a manual release.

This naming creates confusion about which images are production-ready versus pre-production staging.

## 💡 Proposed Solution

Rename the `latest` flow type to `staging` so that any push to the main branch produces `staging-{sha}` tagged images instead of `latest-{sha}`.

### Current Behavior

| Scenario | Flow Type | Tag Pattern | Semantic Issue |
|----------|-----------|-------------|----------------|
| PR (any branch → dev) | `pr` | `pr-{sha}` | ✅ Clear |
| Push to dev | `dev` | `dev-{sha}` | ✅ Clear |
| PR (dev → main) | `dev` | `dev-{sha}` | ✅ Clear |
| PR (any other branch → main) | `patch` | `patch-{sha}` | ✅ Clear |
| **Push to main (merge)** | **`latest`** | **`latest-{sha}`** | ⚠️ **Confusing** |
| Manual release | N/A | Handled by separate workflow | `latest`, `v1.0.0` |

### Proposed Behavior

| Scenario | Flow Type | Tag Pattern | Benefit |
|----------|-----------|-------------|---------|
| PR (any branch → dev) | `pr` | `pr-{sha}` | Feature testing |
| Push to dev | `dev` | `dev-{sha}` | Development images |
| PR (dev → main) | `dev` | `dev-{sha}` | Preview staging |
| PR (any other branch → main) | `patch` | `patch-{sha}` | Emergency patch preview |
| **Push to main (any merge)** | **`staging`** | **`staging-{sha}`** | **Pre-production validation** |
| Manual release | N/A | Handled by separate workflow | True `latest` production tag |

## 🔄 Workflow Clarity

```
Feature Branch --> PR --> dev branch
                           |
                           | (pr-{sha}, dev-{sha})
                           |
                           v
                      PR to main (Preview: dev-{sha})
                           |
Hotfix Branch --> PR to main (Preview: patch-{sha})
                           |
                           v
                      main branch
                           |
                      Auto Build
                           |
                           v
                    staging-{sha} (Pre-production)
                           |
                   Manual Release
                           |
                           v
                  latest + v1.0.x (Production)
```

## 📋 Implementation Changes Needed

### 1. Update `scripts/detect-build-flow.sh` (Lines 188-191)

**Current:**
```bash
# Push to main branch -> Use 'latest' or semantic version
elif [ "$branch" = "$MAIN_BRANCH" ]; then
    flow_type="latest"
    log_success "Flow: Push to main branch (latest)"
```

**Proposed:**
```bash
# Push to main branch -> staging for pre-production validation
elif [ "$branch" = "$MAIN_BRANCH" ]; then
    flow_type="staging"
    log_success "Flow: Push to main branch (staging)"
```

### 2. Update `scripts/pr-comment.js` Flow Metadata

Add `staging` flow metadata:
```javascript
staging: {
  emoji: '🚀',
  title: 'Staging Build',
  description: 'Pre-production validation',
  color: '#ffd700'
}
```

### 3. Update Documentation

- `README.md` - Update flow types table
- Examples section - Add staging flow example
- Flowchart/diagram - Update to show staging flow

## ✅ Benefits

1. **Semantic Clarity**: `staging-{sha}` clearly indicates pre-production status
2. **Pipeline Transparency**: Developers know these images need validation before release
3. **True `latest` Tag**: Reserved for production releases via manual release workflow
4. **Universal Application**: Whether merged from `dev` or emergency `patch`, main branch = staging
5. **Industry Standard**: Aligns with common CI/CD terminology (dev → staging → production)

## 🔍 Use Cases

### Use Case 1: Normal Development Flow
```
feature/api → dev (pr-{sha}, dev-{sha})
           ↓
    PR: dev → main (dev-{sha})
           ↓
   Merge to main (staging-{sha}) ← Pre-production testing
           ↓
  Manual Release (latest, v1.0.4) ← Production
```

### Use Case 2: Emergency Hotfix
```
fix/security → main (patch-{sha})
           ↓
   Merge to main (staging-{sha}) ← Quick validation
           ↓
  Manual Release (latest, v1.0.5) ← Production
```

## 🎯 Expected Outcome

After this change:
- **Development images**: `pr-{sha}`, `dev-{sha}`, `wip-{sha}` 
- **Pre-production/Staging**: `staging-{sha}` (on main branch)
- **Production**: `latest`, `v1.0.x` (manual release only)

Clear separation of concerns and no confusion about which images are production-ready.

## 📝 Notes

- This is a **breaking change** that will affect users relying on `latest-{sha}` tags
- Consider releasing as a new major version (v2.0.0)
- Update changelog and migration guide
- The `patch` flow should continue to work for **any branch** (except dev) targeting main, not just branches named "hotfix"

---

**Priority:** Enhancement  
**Impact:** Improves clarity and aligns with industry-standard CI/CD semantics

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Rename `latest` flow to `staging` for better CI/CD semantics #5

🎯 Problem Statement

💡 Proposed Solution

Current Behavior

Proposed Behavior

🔄 Workflow Clarity

📋 Implementation Changes Needed

1. Update `scripts/detect-build-flow.sh` (Lines 188-191)

2. Update `scripts/pr-comment.js` Flow Metadata

3. Update Documentation

✅ Benefits

🔍 Use Cases

Use Case 1: Normal Development Flow

Use Case 2: Emergency Hotfix

🎯 Expected Outcome

📝 Notes

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Scenario	Flow Type	Tag Pattern	Semantic Issue
PR (any branch → dev)	`pr`	`pr-{sha}`	✅ Clear
Push to dev	`dev`	`dev-{sha}`	✅ Clear
PR (dev → main)	`dev`	`dev-{sha}`	✅ Clear
PR (any other branch → main)	`patch`	`patch-{sha}`	✅ Clear
Push to main (merge)	`latest`	`latest-{sha}`	⚠️ Confusing
Manual release	N/A	Handled by separate workflow	`latest`, `v1.0.0`

Uh oh!

Rename latest flow to staging for better CI/CD semantics #5

Description

🎯 Problem Statement

💡 Proposed Solution

Current Behavior

Proposed Behavior

🔄 Workflow Clarity

📋 Implementation Changes Needed

1. Update scripts/detect-build-flow.sh (Lines 188-191)

2. Update scripts/pr-comment.js Flow Metadata

3. Update Documentation

✅ Benefits

🔍 Use Cases

Use Case 1: Normal Development Flow

Use Case 2: Emergency Hotfix

🎯 Expected Outcome

📝 Notes

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Rename `latest` flow to `staging` for better CI/CD semantics #5

1. Update `scripts/detect-build-flow.sh` (Lines 188-191)

2. Update `scripts/pr-comment.js` Flow Metadata