Create floating v1 tag for stable consumer pinning

[github-actions]

Topic GUID: 10ba1f8c-a439-5769-baad-b111fb1b3f54

Why

Consumers currently must pin to exact versions (e.g., @v1.0.0) or use unstable @main. A floating @v1 tag allows consumers to receive bug fixes automatically while maintaining major version stability, following GitHub Actions best practices.
Scope

• Release management and tag creation.

Tasks

• Create a v1 tag pointing to the latest v1.x release.
• Document the versioning strategy in CHANGELOG.md and docs/INTEGRATION_GUIDE.md.
• Add a GitHub Action or release workflow step that updates the floating tag on each v1.x release.
• Update README.md examples to show both pinned and floating tag usage.

Acceptance criteria

• @v1 tag exists and points to latest v1.x release.
• Consumers can use uses: stranske/Workflows/.github/workflows/reusable-10-ci-python.yml@v1.
• Documentation explains versioning strategy and when to use each approach.

Implementation notes

• Use git tag -f v1 v1.0.0 && git push origin v1 --force pattern in release workflow.
• Consider also creating @v1.0 minor version floating tags for more granular control.

---

Synced by workflow run.

[github-actions]

Branch codex/issue-8 created from main.

Option 1 (Invite) is enforced on issue events. PR creation is disabled by design so you are the PR author. Codex only engages on human-authored PRs.

Please open the PR as the author so Codex can work on it:

• Compare link: https://github.com/stranske/Workflows/compare/main...codex/issue-8?expand=1
• Suggested title: Codex bootstrap for #8
• Suggested body (copy/paste):

### Keepalive: OFF
<!-- meta:issue:8 -->

### Source Issue #8: Create floating v1 tag for stable consumer pinning

Base: main
Head: codex/issue-8

Source: https://github.com/stranske/Workflows/issues/8

> Topic GUID: 10ba1f8c-a439-5769-baad-b111fb1b3f54
> 
> ## Why
> Consumers currently must pin to exact versions (e.g., `@v1.0.0`) or use unstable `@main`. A floating `@v1` tag allows consumers to receive bug fixes automatically while maintaining major version stability, following GitHub Actions best practices.
> Scope
> - Release management and tag creation.
> 
> ## Tasks
> - [ ] Create a `v1` tag pointing to the latest v1.x release.
> - [ ] Document the versioning strategy in CHANGELOG.md and docs/INTEGRATION_GUIDE.md.
> - [ ] Add a GitHub Action or release workflow step that updates the floating tag on each v1.x release.
> - [ ] Update README.md examples to show both pinned and floating tag usage.
> 
> ## Acceptance criteria
> - `@v1` tag exists and points to latest v1.x release.
> - Consumers can use `uses: stranske/Workflows/.github/workflows/reusable-10-ci-python.yml@v1`.
> - Documentation explains versioning strategy and when to use each approach.
> 
> ## Implementation notes
> - Use `git tag -f v1 v1.0.0 && git push origin v1 --force` pattern in release workflow.
> - Consider also creating `@v1.0` minor version floating tags for more granular control.
> 
> ---
> Synced by [workflow run](https://github.com/stranske/Workflows/actions/runs/20392640211).

@codex start

Codex, please derive and propose:
- Scope / key constraints
- Acceptance criteria / definition of done
- Initial task checklist to iterate through

Use the issue details above to draft the plan, then proceed with implementation.

---

Once the plan is posted, comment the snippet below to start execution and enable keepalive:

The following block should be pasted as a separate PR comment:

```markdown
@codex Your objective is to satisfy the **Acceptance Criteria** by completing each **Task** within the defined **Scope**.

**This round you MUST:**
1. Implement actual code or test changes that advance at least one incomplete task toward acceptance.
2. Commit meaningful source code (.py, .yml, .js, etc.)—not just status/docs updates.
3. Mark a task checkbox complete ONLY after verifying the implementation works.
4. **POST A REPLY COMMENT** with completed checkboxes using the **EXACT TEXT** from the lists below.

**CRITICAL - Checkbox Format:**
When posting your reply, copy the **exact checkbox text** from the Tasks and Acceptance Criteria sections below. Do NOT paraphrase or summarize. The automation matches text exactly.

Example format for your reply:

Completed this round

Tasks

• Add an environment flag (e.g., TREND_PIPELINE_PROXY_SIMPLE) that, when set, skips GC scanning...
• Ensure default behaviour remains unchanged (GC scanning enabled) to preserve test friendliness.

Acceptance Criteria

• Setting the new env flag yields a direct-import proxy path; default continues to honour GC-scanned modules.

**DO NOT:**
- Commit only status files, markdown summaries, or documentation when tasks require code.
- Re-post checklists without making implementation progress.
- Close the round without source-code changes when acceptance criteria require them.
- Paraphrase or shorten checkbox text—copy it exactly for tracking to work.

Review the Scope/Tasks/Acceptance below, identify the next incomplete task that requires code, implement it, then **post a reply comment** with the completed items using their **exact original text**.