Create integration test consumer repository

[github-actions]

Topic GUID: 24be3dee-d72e-519e-927f-8b25052b55f9

Why

Currently there's no real-world validation that the reusable workflows work correctly for external consumers. An integration test repo would catch issues before they affect real users.
Scope

• New repository stranske/Workflows-integration-test that consumes this workflow library.

Tasks

• Create minimal Python project repository.
• Configure CI using reusable workflows from stranske/Workflows.
• Add workflow that runs on schedule and on workflow library releases.
• Test multiple configurations: basic, full coverage, monorepo simulation.
• Report integration test status back to main repo via badge or notification.

Acceptance criteria

• Integration test repo exists and runs CI successfully.
• Tests exercise reusable-10-ci-python.yml with various input combinations.
• Failures in integration tests create issues in stranske/Workflows.
• Badge in README.md shows integration test status.

Implementation notes

• Use workflow_dispatch with repository_dispatch to trigger on releases.
• Include edge cases: no pyproject.toml, minimal project, coverage disabled.
• Consider testing @main, @v1, and specific version tags.

---

Synced by workflow run.

[github-actions]

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

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

### Source Issue #17: Create integration test consumer repository

Base: main
Head: codex/issue-17

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

> Topic GUID: 24be3dee-d72e-519e-927f-8b25052b55f9
> 
> ## Why
> Currently there's no real-world validation that the reusable workflows work correctly for external consumers. An integration test repo would catch issues before they affect real users.
> Scope
> - New repository `stranske/Workflows-integration-test` that consumes this workflow library.
> 
> ## Tasks
> - [ ] Create minimal Python project repository.
> - [ ] Configure CI using reusable workflows from stranske/Workflows.
> - [ ] Add workflow that runs on schedule and on workflow library releases.
> - [ ] Test multiple configurations: basic, full coverage, monorepo simulation.
> - [ ] Report integration test status back to main repo via badge or notification.
> 
> ## Acceptance criteria
> - Integration test repo exists and runs CI successfully.
> - Tests exercise reusable-10-ci-python.yml with various input combinations.
> - Failures in integration tests create issues in stranske/Workflows.
> - Badge in README.md shows integration test status.
> 
> ## Implementation notes
> - Use `workflow_dispatch` with `repository_dispatch` to trigger on releases.
> - Include edge cases: no pyproject.toml, minimal project, coverage disabled.
> - Consider testing `@main`, `@v1`, and specific version tags.
> 
> ---
> 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-17.

[github-actions]

PR #44 already exists for branch codex/issue-17. Updated PR body with issue content.

PR link: #44

[stranske]

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