[PR] fix(bitbucket): fail closed for removed cloud issues [magpie]

["KatalKavya96 (via GitHub)" <gi...@apache.org>]

KatalKavya96 opened a new pull request, #1599:
URL: https://github.com/apache/magpie/pull/1599

   <!-- SPDX-License-Identifier: Apache-2.0
        https://www.apache.org/licenses/LICENSE-2.0 -->
   
   ## Summary
   
   - Stops Magpie from calling Bitbucket Cloud's native Issue Tracker API, which Atlassian fully removed on August 20, 2026.
   - Keeps the historical `issue` CLI commands as fail-closed compatibility stubs: issue list/get/comments/comment/attachments now reject before making any HTTP request and direct callers toward linked Jira coverage.
   - Updates the Bitbucket adapter documentation and capability notes so removed native issue functionality is no longer advertised as supported.
   
   ## Type of change
   
   - [ ] Skill change (`.claude/skills/<name>/`) — eval fixtures updated below
   - [x] Tool / bridge contract (`tools/<system>/*.md`)
   - [x] Python package (`tools/*/` with `pyproject.toml`)
   - [ ] Groovy reference impl
   - [ ] Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
   - [x] Documentation (`docs/`, `README.md`, `CONTRIBUTING.md`)
   - [ ] Project template (`projects/_template/`)
   - [ ] CI / dev loop (`prek`, workflows, validators)
   - [ ] Other:
   
   ## Test plan
   
   - [ ] `prek run --all-files` passes
   - [x] For Python packages touched: `uv run pytest` / `ruff check` / `mypy` passes
   - [ ] For Groovy bridges touched: command-line invocation tested end-to-end
   - [ ] For skill changes: eval suite passes for the affected skill
         (`PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner tools/skill-evals/evals/<skill>/`)
   - [ ] For skill *behaviour* changes: a new or updated eval fixture is included in this PR
         (a regression test for the bug fixed / the behaviour added — see CONTRIBUTING.md)
   - [x] Other:
     - Added focused regression coverage for all five native Cloud issue operations.
     - Each affected operation verifies that the HTTP opener is never invoked.
     - Full Bitbucket test suite passes.
     - `git diff --check` passes.
   
   ## RFC-AI-0004 compliance
   
   - [ ] **HITL** — any new mutation is gated on explicit user confirmation
   - [x] **Sandbox** — no new unrestricted host access; the removed issue paths now fail before any network request
   - [x] **Vendor neutrality** — removed Bitbucket-native tracker behavior is no longer presented as usable `contract:tracker` coverage; callers are directed toward the separate linked Jira adapter path
   - [ ] **Conversational + correctable** — agentic-override path documented if behaviour is adopter-tunable
   - [x] **Write-access discipline** — the obsolete native issue-comment write path can no longer perform an outbound mutation
   - [ ] **Privacy LLM** — private content does not reach a non-approved LLM; redactor invoked where needed
   
   ## Linked issues
   
   Refs #606
   
   ## Notes for reviewers (optional)
   
   Atlassian fully removed the native Bitbucket Cloud Issue Tracker API on August 20, 2026. The bridge still contained working implementations for:
   
   - `issue list-open`
   - `issue get <id>`
   - `issue comments <id>`
   - `issue comment <id> --body-file <path>`
   - `issue attachments <id>`
   
   Those commands could therefore attempt requests against API endpoints that no longer exist.
   
   This change intentionally keeps the CLI surface rather than removing the commands outright, so existing callers receive an explicit and actionable error instead of an argparse/command-not-found break. Each native Cloud issue operation now fails closed before constructing or sending an HTTP request and points callers toward linked Jira coverage.
   
   The normalization helpers and historical payload fixtures remain in place; this PR changes the reachable runtime behavior rather than deleting historical response-shape support.
   
   Data Center native issue operations were already unsupported and remain unchanged.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] fix(bitbucket): fail closed for removed cloud issues [magpie]

["KatalKavya96 (via GitHub)" <gi...@apache.org>]

KatalKavya96 commented on PR #1599:
URL: https://github.com/apache/magpie/pull/1599#issuecomment-6200437445

   Thanks @Kaap10 — good catch on the central capability registry.
   
   I’ve updated `docs/labels-and-capabilities.md` so the Bitbucket entry no longer advertises the removed native Cloud issue operations and now records the fail-closed compatibility surface plus the linked Jira direction.
   
   For the optional end-to-end CLI exit-code test, I’m keeping the current scope as-is for now since the focused regression tests already cover all five removed Cloud issue operations and assert that no HTTP request is made.
   
   Thanks for testing this locally as well!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] fix(bitbucket): fail closed for removed cloud issues [magpie]

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk merged PR #1599:
URL: https://github.com/apache/magpie/pull/1599


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org