Create GitHub starter workflow template

[github-actions]

Topic GUID: b4db7d20-aa6a-58dd-b5b2-3636837d50ad

Why

GitHub's "Actions → New workflow" UI shows starter workflows from .github/workflow-templates/. Adding templates here makes the workflow library discoverable directly in GitHub's UI for repos that have access.
Scope

• Create .github/workflow-templates/ directory with template files.

Tasks

• Create workflow-templates/python-ci.yml based on templates/ci-basic.yml.
• Create workflow-templates/python-ci.properties.json with metadata.
• Add icon and description for GitHub UI display.
• Test that templates appear in "Actions → New workflow" for authorized repos.

Acceptance criteria

• Template appears in GitHub Actions UI when creating new workflow.
• One-click creates a working CI workflow using reusable workflows.
• Properties file includes appropriate categories and description.

Implementation notes

• GitHub requires specific file naming: {name}.yml + {name}.properties.json.
• Templates must be in default branch to appear in UI.
• Consider multiple templates: basic, full, with-docker.

---

Synced by workflow run.

[github-actions]

Branch codex/issue-15 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-15?expand=1
• Suggested title: Codex bootstrap for #15
• Suggested body (copy/paste):

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

### Source Issue #15: Create GitHub starter workflow template

Base: main
Head: codex/issue-15

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

> Topic GUID: b4db7d20-aa6a-58dd-b5b2-3636837d50ad
> 
> ## Why
> GitHub's "Actions → New workflow" UI shows starter workflows from `.github/workflow-templates/`. Adding templates here makes the workflow library discoverable directly in GitHub's UI for repos that have access.
> Scope
> - Create `.github/workflow-templates/` directory with template files.
> 
> ## Tasks
> - [ ] Create `workflow-templates/python-ci.yml` based on templates/ci-basic.yml.
> - [ ] Create `workflow-templates/python-ci.properties.json` with metadata.
> - [ ] Add icon and description for GitHub UI display.
> - [ ] Test that templates appear in "Actions → New workflow" for authorized repos.
> 
> ## Acceptance criteria
> - Template appears in GitHub Actions UI when creating new workflow.
> - One-click creates a working CI workflow using reusable workflows.
> - Properties file includes appropriate categories and description.
> 
> ## Implementation notes
> - GitHub requires specific file naming: `{name}.yml` + `{name}.properties.json`.
> - Templates must be in default branch to appear in UI.
> - Consider multiple templates: basic, full, with-docker.
> 
> ---
> Synced by [workflow run](https://github.com/stranske/Workflows/actions/runs/20392702689).

@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**.

[stranske]

Codex belt dispatcher queued this issue and created branch codex/issue-15.

[github-actions]

PR #38 already exists for branch codex/issue-15. Updated PR body with issue content.

PR link: #38

[stranske]

Codex belt dispatcher queued this issue and created branch codex/issue-15.

[stranske]

Codex belt dispatcher queued this issue and created branch codex/issue-15.

[stranske]

Codex belt dispatcher queued this issue and created branch codex/issue-15.

[stranske]

Codex belt dispatcher queued this issue and created branch codex/issue-15.

[stranske]

Codex belt dispatcher queued this issue and created branch codex/issue-15.

[stranske]

Codex belt dispatcher queued this issue and created branch codex/issue-15.