Test Suite C: Deduplication Functional Tests

[stranske]

Why

Test the agents-dedup.yml workflow with real issues in a consumer repo.

Test the agents-dedup.yml workflow with real issues in a consumer repo.

Scope

Part of Phase 3 workflow rollout validation per langchain-post-code-rollout.md

Part of Phase 3 workflow rollout validation per langchain-post-code-rollout.md

Part of Phase 3 workflow rollout validation per langchain-post-code-rollout.md

</details>

Non-Goals

[ ] Not provided.

-Not provided.

Tasks

• Create an issue that duplicates an existing issue in the Manager-Database repo.
  • Define scope for: Identify an existing issue in the Manager-Database repo. (verify: confirm completion in repo)
  • Implement focused slice for: Identify an existing issue in the Manager-Database repo. (verify: confirm completion in repo)
  • Validate focused slice for: Identify an existing issue in the Manager-Database repo. (verify: confirm completion in repo)
  • Define scope for: Create a duplicate issue based on the identified existing issue. (verify: confirm completion in repo)
  • Implement focused slice for: Create a duplicate issue based on the identified existing issue. (verify: confirm completion in repo)
  • Validate focused slice for: Create a duplicate issue based on the identified existing issue. (verify: confirm completion in repo)
• Verify that the duplicate issue is detected and linked to the original issue.
  • Check if the duplicate issue is detected. (verify: confirm completion in repo)
  • Define scope for: Check if the duplicate issue is linked to the original issue. (verify: confirm completion in repo)
  • Implement focused slice for: Check if the duplicate issue is linked to the original issue. (verify: confirm completion in repo)
  • Validate focused slice for: Check if the duplicate issue is linked to the original issue. (verify: confirm completion in repo)
• Create a unique issue with no duplicates in the Manager-Database repo.
• Confirm that the unique issue passes clean with no duplicate flags.
  • Define scope for: Define scope for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Implement focused slice for: Define scope for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Validate focused slice for: Define scope for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Define scope for: Implement focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Implement focused slice for: Implement focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Validate focused slice for: Implement focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Define scope for: Validate focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Implement focused slice for: Validate focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Validate focused slice for: Validate focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Verify that there are no duplicate flags on the unique issue.
• Create an issue that duplicates an existing issue in the Manager-Database repo.
  • Define scope for: Identify an existing issue in the Manager-Database repo. (verify: confirm completion in repo)
  • Implement focused slice for: Identify an existing issue in the Manager-Database repo. (verify: confirm completion in repo)
  • Validate focused slice for: Identify an existing issue in the Manager-Database repo. (verify: confirm completion in repo)
  • Define scope for: Create a duplicate issue based on the identified existing issue. (verify: confirm completion in repo)
  • Implement focused slice for: Create a duplicate issue based on the identified existing issue. (verify: confirm completion in repo)
  • Validate focused slice for: Create a duplicate issue based on the identified existing issue. (verify: confirm completion in repo)
• Verify that the duplicate issue is detected and linked to the original issue.
  • Check if the duplicate issue is detected. (verify: confirm completion in repo)
  • Define scope for: Check if the duplicate issue is linked to the original issue. (verify: confirm completion in repo)
  • Implement focused slice for: Check if the duplicate issue is linked to the original issue. (verify: confirm completion in repo)
  • Validate focused slice for: Check if the duplicate issue is linked to the original issue. (verify: confirm completion in repo)
• Create a unique issue with no duplicates in the Manager-Database repo.
• Confirm that the unique issue passes clean with no duplicate flags.
  • Define scope for: Define scope for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Implement focused slice for: Define scope for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Validate focused slice for: Define scope for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Define scope for: Implement focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Implement focused slice for: Implement focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Validate focused slice for: Implement focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Define scope for: Validate focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Implement focused slice for: Validate focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Validate focused slice for: Validate focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo)
  • Verify that there are no duplicate flags on the unique issue.

Acceptance Criteria

• DDPT01 detects and links duplicate.
• DDPT02 allows unique issues through.
• DDPT01 detects and links duplicate.
• DDPT02 allows unique issues through.
• DDPT01 detects and links duplicate
• DDPT02 allows unique issues through
• ### Test Repo
• Run tests in Manager-Database or another consumer repo.

Implementation Notes

Run tests in Manager-Database or another consumer repo.

Original Issue

_Run tests in Manager-Database or another consumer repo._

<details>
<summary>Original Issue</summary>

```text
## Phase 3 Functional Testing - Issue Deduplication

Test the `agents-dedup.yml` workflow with real issues in a consumer repo.

### Test Cases

| ID | Test | Expected Result |
|----|------|-----------------|
| DDPT01 | Create issue that duplicates an existing issue | Detects duplicate, links to original, suggests closing |
| DDPT02 | Create unique issue with no duplicates | Passes clean, no duplicate flags |

[github-actions]

Issue Optimization Suggestions

Review the suggestions below. If you want the agent to apply them, add the
agents:apply-suggestions label to this issue.

Task splitting

• Create an issue that duplicates an existing issue in the Manager-Database repo. (This task could involve multiple steps, such as identifying the existing issue and creating the duplicate.). Suggested split: Identify an existing issue in the Manager-Database repo. (verify: confirm completion in repo), Create a duplicate issue based on the identified existing issue. (verify: confirm completion in repo).
• Verify that the duplicate issue is detected and linked to the original issue. (Verification may require multiple checks and confirmations.). Suggested split: Check if the duplicate issue is detected. (verify: confirm completion in repo), Check if the duplicate issue is linked to the original issue. (verify: confirm completion in repo).
• Confirm that the unique issue passes clean with no duplicate flags. (Confirmation may involve multiple checks.). Suggested split: Define scope for: Check if the unique issue is created successfully. (verify: confirm completion in repo), Implement focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo), Validate focused slice for: Check if the unique issue is created successfully. (verify: confirm completion in repo), Verify that there are no duplicate flags on the unique issue..

Blocked tasks

• None

Objective acceptance criteria

• DDPT01 detects and links duplicate. (Subjective acceptance criteria. | Specify that the system must return a confirmation message indicating the duplicate was detected and linked.)
• DDPT02 allows unique issues through. (Subjective acceptance criteria. | Specify that the system must return a confirmation message indicating the unique issue was accepted without flags.)

Missing sections

• None

Formatting issues

• Bullets used for non-tasks in the Non-Goals section.
• Inconsistent use of headings (e.g., 'Why' vs 'Context').

Notes

• The issue is generally well-structured but could benefit from clearer task definitions and more objective acceptance criteria.

[github-actions]

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

<!-- meta:issue:692 -->

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

## Keepalive Next Task

**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. Focus on the FIRST unchecked task unless blocked, then move to the next.

**Guidelines:**
- Keep edits scoped to the current task rather than reshaping the entire PR.
- Use repository instructions, conventions, and tests to validate work.
- Prefer small, reviewable commits; leave clear notes when follow-up is required.
- Do NOT work on unrelated improvements until all PR tasks are complete.

**COVERAGE TASKS - SPECIAL RULES:**
If a task mentions "coverage" or a percentage target (e.g., "≥95%", "to 95%"), you MUST:
1. After adding tests, run TARGETED coverage verification to avoid timeouts:
   - For a specific script like `scripts/foo.py`, run:
     `pytest tests/scripts/test_foo.py --cov=scripts/foo --cov-report=term-missing -m "not slow"`
   - If no matching test file exists, run:
     `pytest tests/ --cov=scripts/foo --cov-report=term-missing -m "not slow" -x`
2. Find the specific script in the coverage output table
3. Verify the `Cover` column shows the target percentage or higher
4. Only mark the task complete if the actual coverage meets the target
5. If coverage is below target, add more tests until it meets the target

IMPORTANT: Always use `-m "not slow"` to skip slow integration tests that may timeout.
IMPORTANT: Use targeted `--cov=scripts/specific_module` instead of `--cov=scripts` for faster feedback.

A coverage task is NOT complete just because you added tests. It is complete ONLY when the coverage command output confirms the target is met.

**The Tasks and Acceptance Criteria are provided in the appendix below.** Work through them in order.

<!-- 
  DO NOT ADD TASK CONTENT BELOW THIS LINE
  
  Task content is dynamically injected from the PR body via the `appendix` input.
  This template file should only contain instructions, not PR-specific tasks.
  
  If you see task content in this file, it was incorrectly committed and should
  be removed. The guard script will flag this as an error.
-->