cleveragents/cleveragents-core

Fork 3

[AUTO-SPEC] ⚠️ ADR-049 Conflict: Two PRs claim same ADR number with contradictory content #10056

New issue

Open

opened 2026-04-16 20:18:35 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-16 20:18:35 +00:00

Owner

ADR-049 Conflict Alert

Two open PRs are both attempting to create ADR-049 with different, potentially contradictory content. This will cause a merge conflict and represents an architectural decision conflict.

Conflicting PRs

PR #10009 — `docs/adr/ADR-049-cli-communication-pattern.md`

Title: docs(spec): fix invariant reconciliation, add ACMS thread safety, v3.6.0 section, ADR-049
Branch: spec/auto-arch-23-spec-updates
ADR Content: CLI communication pattern — documents that local CLI is exempt from the A2A boundary requirement, with an import-linter configuration and M9 migration path to full A2A adoption
Architectural stance: CLI can bypass A2A boundary (exemption)

PR #10052 — `docs/adr/ADR-049-a2a-boundary-enforcement.md`

Title: docs(spec): add ADR-049 and layer boundary enforcement specification [AUTO-ARCH-24]
Branch: spec/auto-arch-24-a2a-boundary-enforcement-adr
ADR Content: A2A boundary enforcement — documents that A2A is the sole communication channel between Presentation and Application layers, with all direct imports forbidden
Architectural stance: Strict A2A enforcement (no exemptions)

Why This Is Critical

Contradictory decisions: PR #10009 says CLI can bypass A2A; PR #10052 says CLI cannot bypass A2A. These are mutually exclusive architectural stances.
Same ADR number: Both claim ADR-049, so only one can exist.
Merge conflict: If either PR is merged, the other will have a conflict on the ADR file.
Spec integrity: The specification cannot have contradictory architectural decisions.

Required Human Action

A human architect needs to:

Decide the architectural stance: Should CLI be exempt from A2A boundary, or should strict enforcement apply?
Choose which PR to merge: Based on the decision, select the appropriate PR.
Renumber or close the other PR: The rejected ADR should either be renumbered (ADR-050?) or closed.
Update issue #9962: The architectural violation issue should be resolved consistently with the decision.

Issue #9962: [AUTO-GUARD-1] Module Coupling: CLI and Application layers bypass A2A boundary
PR #10009: docs(spec): fix invariant reconciliation, add ACMS thread safety, v3.6.0 section, ADR-049
PR #10052: docs(spec): add ADR-049 and layer boundary enforcement specification [AUTO-ARCH-24]

Automated by CleverAgents Bot
Supervisor: Spec Update | Agent: spec-update-pool-supervisor

## ADR-049 Conflict Alert Two open PRs are both attempting to create `ADR-049` with different, potentially contradictory content. This will cause a merge conflict and represents an architectural decision conflict. ## Conflicting PRs ### PR #10009 — `docs/adr/ADR-049-cli-communication-pattern.md` - **Title**: docs(spec): fix invariant reconciliation, add ACMS thread safety, v3.6.0 section, ADR-049 - **Branch**: `spec/auto-arch-23-spec-updates` - **ADR Content**: CLI communication pattern — documents that local CLI is **exempt** from the A2A boundary requirement, with an import-linter configuration and M9 migration path to full A2A adoption - **Architectural stance**: CLI can bypass A2A boundary (exemption) ### PR #10052 — `docs/adr/ADR-049-a2a-boundary-enforcement.md` - **Title**: docs(spec): add ADR-049 and layer boundary enforcement specification [AUTO-ARCH-24] - **Branch**: `spec/auto-arch-24-a2a-boundary-enforcement-adr` - **ADR Content**: A2A boundary enforcement — documents that A2A is the **sole** communication channel between Presentation and Application layers, with all direct imports forbidden - **Architectural stance**: Strict A2A enforcement (no exemptions) ## Why This Is Critical 1. **Contradictory decisions**: PR #10009 says CLI can bypass A2A; PR #10052 says CLI cannot bypass A2A. These are mutually exclusive architectural stances. 2. **Same ADR number**: Both claim ADR-049, so only one can exist. 3. **Merge conflict**: If either PR is merged, the other will have a conflict on the ADR file. 4. **Spec integrity**: The specification cannot have contradictory architectural decisions. ## Required Human Action A human architect needs to: 1. **Decide the architectural stance**: Should CLI be exempt from A2A boundary, or should strict enforcement apply? 2. **Choose which PR to merge**: Based on the decision, select the appropriate PR. 3. **Renumber or close the other PR**: The rejected ADR should either be renumbered (ADR-050?) or closed. 4. **Update issue #9962**: The architectural violation issue should be resolved consistently with the decision. ## Related Issues - Issue #9962: [AUTO-GUARD-1] Module Coupling: CLI and Application layers bypass A2A boundary - PR #10009: docs(spec): fix invariant reconciliation, add ACMS thread safety, v3.6.0 section, ADR-049 - PR #10052: docs(spec): add ADR-049 and layer boundary enforcement specification [AUTO-ARCH-24] --- **Automated by CleverAgents Bot** Supervisor: Spec Update | Agent: spec-update-pool-supervisor

HAL9000 commented

2026-04-16 20:41:31 +00:00

Author

Owner

URGENT: Human Decision Required — ADR-049 Architectural Conflict

This is a critical architectural conflict that requires an immediate human decision. Two open PRs are claiming the same ADR number (ADR-049) with mutually exclusive architectural stances.

The Conflict

	PR #10009	PR #10052
ADR file	`ADR-049-cli-communication-pattern.md`	`ADR-049-a2a-boundary-enforcement.md`
Stance	CLI is exempt from A2A boundary	A2A is the sole communication channel — no exemptions
Author	Architecture agent [AUTO-ARCH-23]	Architecture agent [AUTO-ARCH-24]
Created	2026-04-16T12:10Z	2026-04-16T19:34Z

Why This Cannot Be Resolved Automatically

This is a fundamental architectural decision about whether the CLI layer can directly import from the Application layer:

Option A (PR #10009): Allow CLI exemption with a migration path to full A2A in M9. This is pragmatic but creates a known boundary violation.
Option B (PR #10052): Enforce strict A2A boundaries immediately. This is architecturally clean but requires fixing 83+ existing CLI imports.

Both options are valid architectural choices, but they cannot coexist. A human architect must decide.

Recommended Action

Review both PRs:
- PR #10009: #10009
- PR #10052: #10052
Choose the architectural stance that aligns with the project's current priorities
Comment on this issue with your decision:
- "Approve PR #10009 (CLI exemption)" — or —
- "Approve PR #10052 (strict enforcement)"
The rejected PR should be closed or renumbered to ADR-050

Impact of Delay

Both PRs are currently blocked with Needs Feedback labels. The autonomous agent system will not merge either PR until a human decision is made. However, the conflict will continue to exist and may cause confusion for other agents working on related issues.

Timeout: If no response is received within 48 hours (by 2026-04-18T20:18Z), the Human Liaison Supervisor will post a reminder and escalate further.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: human-liaison-pool-supervisor
Worker: [AUTO-HUMAN-5]

## URGENT: Human Decision Required — ADR-049 Architectural Conflict This is a critical architectural conflict that requires an immediate human decision. Two open PRs are claiming the same ADR number (ADR-049) with **mutually exclusive** architectural stances. ### The Conflict | | PR #10009 | PR #10052 | |---|---|---| | **ADR file** | `ADR-049-cli-communication-pattern.md` | `ADR-049-a2a-boundary-enforcement.md` | | **Stance** | CLI is **exempt** from A2A boundary | A2A is the **sole** communication channel — no exemptions | | **Author** | Architecture agent [AUTO-ARCH-23] | Architecture agent [AUTO-ARCH-24] | | **Created** | 2026-04-16T12:10Z | 2026-04-16T19:34Z | ### Why This Cannot Be Resolved Automatically This is a fundamental architectural decision about whether the CLI layer can directly import from the Application layer: - **Option A (PR #10009)**: Allow CLI exemption with a migration path to full A2A in M9. This is pragmatic but creates a known boundary violation. - **Option B (PR #10052)**: Enforce strict A2A boundaries immediately. This is architecturally clean but requires fixing 83+ existing CLI imports. Both options are valid architectural choices, but they cannot coexist. A human architect must decide. ### Recommended Action 1. Review both PRs: - PR #10009: https://git.cleverthis.com/cleveragents/cleveragents-core/pulls/10009 - PR #10052: https://git.cleverthis.com/cleveragents/cleveragents-core/pulls/10052 2. Choose the architectural stance that aligns with the project's current priorities 3. Comment on this issue with your decision: - "Approve PR #10009 (CLI exemption)" — or — - "Approve PR #10052 (strict enforcement)" 4. The rejected PR should be closed or renumbered to ADR-050 ### Impact of Delay Both PRs are currently blocked with `Needs Feedback` labels. The autonomous agent system will not merge either PR until a human decision is made. However, the conflict will continue to exist and may cause confusion for other agents working on related issues. **Timeout**: If no response is received within 48 hours (by 2026-04-18T20:18Z), the Human Liaison Supervisor will post a reminder and escalate further. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: human-liaison-pool-supervisor Worker: [AUTO-HUMAN-5]

Rows
Columns