Hide the fetch-service command line option, and warn it's experimental
Metadata
Current evaluation
Closed without implementation or resolution details. An internal Jira ticket was created, but no code changes or merge information were provided, indicating the request was likely deferred or abandoned.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Hide the fetch-service command line option, and warn it's experimental
### Why it needs to get done
.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation or resolution details. An internal Jira ticket was created, but no code changes or merge information were provided, indicating the request was likely deferred or abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned in this repository. Closed without implementation and synchronized to internal Jira ticket CRAFT-3436 for tracking. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without public resolution. The request to hide the fetch-service CLI option and mark it experimental was not implemented or merged. An internal Jira ticket was created, indicating the change was deferred or handled outside the repository. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #487 Allow strict fetch-service sessions on the command-line | craft-application | closed | Closed after UX discussion for --use-fetch-service=strict and --use-fetch-service=permissive CLI flags. No implementation or PR was created, indicating the feature was abandoned or deferred. | |
| #496 feat: mark the fetch-service integration as experimental | craft-application | merged | Merged pull request marking the fetch-service integration as experimental by hiding its CLI option and adding a development warning. Approved by three reviewers, passed CI, and resolved issue #488 with 30 additions and 7 deletions across three files. |