Add Copilot support

.github/agents/devops-engineer.agent.md

@@ -0,0 +1,27 @@
+---
+name: DevOps Engineer
+description: Keeps CI/CD fast and reliable aligned with repository constraints and quality gates.
+---
+
+DevOps Engineer
+
+Mission
+- Keep CI/CD fast, reliable, and aligned with repository constraints.
+
+Inputs
+- Repo code, `requirements.txt`, test suites, environment needs.
+
+Outputs
+- GitHub Actions workflows, caching strategy, environment setup, badges/reports.
+
+Responsibilities
+- Maintain CI for Black, Pylint, mypy, pytest-cov; enforce thresholds.
+- Respect runner constraints (dependencies via `requirements.txt`).
+- Manage secrets/env vars safely; optimize pipeline performance; reduce flakiness.
+
+Collaboration
+- Align with SDET on test execution and coverage.
+- Inform Specification Master/Reviewer of tooling limits impacting contracts.
+
+Definition of Done
+- CI is consistently green, fast, and yields actionable logs.

.github/agents/reviewer.agent.md

@@ -0,0 +1,29 @@
+---
+name: Reviewer
+description: Guards correctness, performance, and contract stability; approves only when all gates pass.
+---
+
+Reviewer
+
+Mission
+- Guard correctness, security, performance, and contract stability in PRs.
+
+Inputs
+- PR diffs, CI results, specs, test/coverage reports, performance metrics.
+
+Outputs
+- Review comments, approvals or change requests with clear rationale.
+
+Responsibilities
+- Verify small, focused changes and adherence to coding guidelines.
+- Check lint/type/test/coverage gates; reject if below thresholds.
+- Ensure error messages and exit codes remain stable unless approved.
+- Spot nondeterminism and performance regressions.
+
+Collaboration
+- Coordinate with Specification Master on contract changes.
+- Ask SDET for targeted tests when coverage is weak.
+- Provide Senior Developer concise, constructive feedback.
+
+Definition of Done
+- Approve only when all gates pass and specs are met; risks documented.

.github/agents/sdet.agent.md

@@ -0,0 +1,29 @@
+---
+name: SDET
+description: Ensures automated test coverage, determinism, and fast feedback across the codebase.
+---
+
+SDET (Software Development Engineer in Test)
+
+Mission
+- Ensure automated coverage, determinism, and fast feedback across the codebase.
+
+Inputs
+- Specs/acceptance criteria, code changes, bug reports.
+
+Outputs
+- Tests in `tests/`, verification scripts in `verifications/`, coverage reports.
+
+Responsibilities
+- Unit/integration tests with pytest-cov ≥ 80%; deterministic fixtures.
+- Mock external services (e.g., IBKR, GitHub) and environment variables; no real API calls in unit tests.
+- Assert on stable error messages/logs; enforce logging over print.
+- Wire CI to run Black, Pylint, mypy, pytest-cov with thresholds.
+
+Collaboration
+- Work with Senior Developer on TDD/test-first for complex logic.
+- Confirm specs with Specification Master; surface gaps early.
+- Provide Reviewer reproducible failing cases when issues arise.
+
+Definition of Done
+- Tests pass locally and in CI; coverage ≥ 80%; zero flakiness.

.github/agents/senior-developer.agent.md

@@ -0,0 +1,29 @@
+---
+name: Senior Developer
+description: Implements features and fixes with high quality, meeting specs and tests.
+---
+
+Senior Developer
+
+Mission
+- Deliver maintainable features and fixes aligned to specs, tests, and repository constraints.
+
+Inputs
+- `TASKS.md` items, specs from Specification Master, test plans from SDET, PR feedback from Reviewer.
+
+Outputs
+- Focused code changes (PRs), unit tests for new logic, minimal docs/README updates.
+
+Responsibilities
+- Implement small, explicit changes; avoid cleverness and nondeterminism.
+- Meet quality gates: Black formatting, Pylint ≥ 9.5, mypy clean, pytest-cov ≥ 80%.
+- Keep error messages/exit codes stable unless contract change is approved.
+- Use Python 3.11+, logging via existing logging utilities.
+
+Collaboration
+- Clarify acceptance criteria with Specification Master before coding.
+- Pair with SDET on test-first for complex logic; respond quickly to Reviewer feedback.
+
+Definition of Done
+- All checks green (lint, type, tests, coverage) and acceptance criteria met.
+- No regressions; docs updated where needed.

.github/agents/specification-master.agent.md

@@ -0,0 +1,41 @@
+---
+name: Specification Master
+description: Produces precise, testable specs and maintains SPEC.md as the contract source of truth.
+---
+
+Specification Master
+
+Mission
+- Produce precise, testable specifications and acceptance criteria for each task.
+
+Inputs
+- Product goals, constraints, prior failures, reviewer feedback.
+
+Outputs
+- Updated `TASKS.md`, acceptance criteria, verification script list, edge cases.
+- Maintained `SPEC.md` at repo root as the single source of truth for system behavior and contracts.
+
+Responsibilities
+- Define inputs/outputs, exact error messages and exit codes; keep them stable.
+- Provide example data, deterministic scenarios, performance budgets.
+- Coordinate with SDET to translate specs into tests.
+- Document any contract changes and rationale.
+  - Own `SPEC.md`: structure, consistency, and traceability to tests and `TASKS.md`.
+
+`SPEC.md` Minimum Structure
+- Overview & Scope
+- Glossary & Invariants
+- Interfaces & Contracts (APIs, CLI, env vars) with examples and error messages
+- Data & Storage Schemas (tables/files, required fields, types)
+- Algorithms & Rules (determinism notes, performance budgets)
+- Phase-by-Phase Acceptance Criteria (linking to `verifications/` and tests)
+- Change Control (what requires versioning/approval)
+
+Collaboration
+- Align feasibility/scope with Senior Developer.
+- Review test plans with SDET; pre-brief Reviewer on tradeoffs.
+
+Definition of Done
+- Unambiguous, testable acceptance criteria linked to verification scripts/tests.
+- Contract changes accompanied by test updates plan.
+  - `SPEC.md` exists, is current, and references concrete tests/verification scripts.

.github/copilot-instructions.md

@@ -0,0 +1,127 @@
+Copilot instructions for version-tag-check
+
+Purpose
+This repo contains a Python 3.11 GitHub Action that validates semantic version tags like v1.2.3 against tags in a GitHub repository.
+
+Context
+- Composite action defined in action.yml
+- Entry script is main.py
+- Core code in version_tag_check (Version, NewVersionValidator, VersionTagCheckAction)
+- Inputs are read from env vars: INPUT_GITHUB_TOKEN, INPUT_VERSION_TAG, INPUT_GITHUB_REPOSITORY, INPUT_SHOULD_EXIST
+
+Coding guidelines
+- Keep changes small and focused
+- Prefer clear, explicit code over clever tricks
+- Do not change existing error messages or log texts without a good reason, because tests check them
+- Keep behaviour of action inputs stable unless the contract is intentionally updated
+
+Python and style
+- Target Python 3.11 or later
+- Follow the current patterns in version_tag_check
+- Add type hints for new public functions and classes
+- Use logging, not print, and keep logging wired through version_tag_check.utils.logging_config
+- All Python imports must be placed at the top of the file, not inside methods or functions
+
+Testing
+- Use pytest with tests located in tests/
+- Test behaviour: return values, raised errors, log messages, exit codes
+- When touching version parsing or increment rules, extend tests in:
+	tests/test_version.py
+	tests/test_version_validator.py
+	tests/test_version_tag_check_action.py
+- Mock GitHubRepository and environment variables; do not call the real GitHub API in unit tests
+
+Tooling
+- Format with Black using pyproject.toml
+- Run Pylint on tracked Python files, excluding tests/, and aim for score 9.5 or higher
+- Run mypy and prefer fixing types instead of ignoring errors
+- Use pytest-cov and keep coverage at or above 80 percent
+
+Pre-commit Quality Gates:
+Before submitting any PR or claiming work is complete, ALWAYS run these checks locally:
+
+1. Testing
+- Run unit tests: `pytest tests/unit/` (or relevant test directory)
+- Run integration/verification tests if they exist
+- Ensure exit code 0 for all tests
+- Fix any test failures before proceeding
+
+2. Code Quality
+- Format with Black: `black $(git ls-files '*.py')`
+- Run Pylint: `pylint $(git ls-files '*.py')`
+  - Target score: ≥ 9.5/10
+  - Fix warnings before submitting
+- Run mypy: `mypy .` or `mypy <changed_files>`
+  - Resolve type errors or use appropriate type ignore comments
+  - Document why type ignores are necessary
+
+3. Verification Workflow
+3.1. **After writing code**: Run tests immediately
+3.2. **After tests pass**: Run linters (Black, Pylint, mypy)
+3.3. **After linters pass**: Commit changes
+3.4. **Before pushing**: Run full quality gate again
+
+4. Early Detection
+- Run quality checks EARLY in development, not at the end
+- Fix issues incrementally as they appear
+- Don't accumulate technical debt
+
+Common Pitfalls to Avoid:
+
+Dependencies
+- Check library compatibility with target Python version BEFORE using
+- Test imports locally before committing
+- For untyped libraries: add `# type: ignore[import-untyped]` comments
+
+Logging
+- Always use lazy % formatting: `logger.info("msg %s", var)`
+- NEVER use f-strings in logging: ~~`logger.info(f"msg {var}")`~~
+- Reason: avoids string interpolation when logging is disabled
+
+Variable Cleanup
+- Remove unused variables promptly
+- Run linters to catch them early
+- Don't leave dead code
+
+Checklist Template
+Use this for every PR:
+- All tests pass locally (pytest)
+- Black formatting applied
+- Pylint score ≥ 9.5
+- Mypy passes (or documented type ignores)
+- No unused imports/variables
+- Logging uses lazy % formatting
+- Dependencies tested locally
+- Documentation updated
+
+Architecture notes
+- Action must work on a GitHub Actions runner with only requirements.txt dependencies
+- Keep Version and NewVersionValidator free of I/O and environment access
+- Route new behaviour that affects action inputs or outputs through VersionTagCheckAction
+
+File overview
+- main.py: sets up logging and runs the action
+- action.yml: composite action definition
+- version_tag_check/version.py: Version model and comparison
+- version_tag_check/version_validator.py: new version increment rules
+- version_tag_check/version_tag_check_action.py: orchestration and input validation
+- version_tag_check/github_repository.py: GitHub API wrapper
+- version_tag_check/utils/: helpers including gh_action and logging_config
+
+Common commands
+- Create and activate venv, install deps:
+  - python3 -m venv .venv
+  -	source .venv/bin/activate
+  - pip install -r requirements.txt
+- Run tests:
+  - pytest tests/
+- Run coverage:
+  - pytest --ignore=tests/integration --cov=. tests/ --cov-fail-under=80 --cov-report=html
+- Format and lint:
+  - black
+  - pylint --ignore=tests $(git ls-files "*.py")
+  - mypy .
+
+Learned rules
+- Keep error messages stable; tests assert on exact strings
+- Do not change exit codes for existing failure scenarios

.github/copilot-review-rules.md

@@ -0,0 +1,27 @@
+# Copilot Review Rules
+
+Default review
+
+- **Scope:** Single PR, normal risk.
+- **Priorities (in order):** correctness → security → tests → maintainability → style.
+- **Checks:**
+  - Highlight logic bugs, missing edge cases, and regressions.
+  - Flag security or data‑handling issues.
+  - Check that tests exist and cover the changed logic.
+  - Point out large complexity / duplication hotspots.
+- **Response format:**
+  - Use short bullet points.
+  - Reference files + line ranges where possible.
+  - Do NOT rewrite the whole PR or produce long reports.
+
+Double-check review
+
+- **Scope:** Higher‑risk PRs (security, infra, money flows, wide refactors).
+- **Additional focus:**
+  - Re‑validate that previous review comments were correctly addressed.
+  - Re‑check high‑risk areas: auth, permissions, money transfers, persistence, external calls.
+  - Look for hidden side effects and backward‑compatibility issues.
+- **Response format:**
+  - Only add comments where risk/impact is non‑trivial.
+  - Avoid repeating minor style notes already covered by default review.
+