[PR] fix(marketplace): sync magpie-utilities plugin with report-framework-issue skill [magpie]

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

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

   <!-- SPDX-License-Identifier: Apache-2.0
        https://www.apache.org/licenses/LICENSE-2.0 -->
   
   ## Summary
   
   - `main` is red: the `check-family-plugins` prek hook fails with
     `magpie-utilities: missing symlink for 'report-framework-issue'
     (family=utilities)`, and every PR built against `main` inherits the
     failure (e.g. the [prek run on main](https://github.com/apache/magpie/actions/runs/32178573003)).
   - Cause is a semantic conflict between two PRs that were each green on
     their own: [apache/magpie#922](https://github.com/apache/magpie/pull/922)
     added the `report-framework-issue` skill with `family: utilities`
     *before* the hook existed, while
     [apache/magpie#907](https://github.com/apache/magpie/pull/907)
     generated the family plugins (and introduced the hook) from a branch
     that predated #922's merge — so the generated `magpie-utilities`
     plugin never picked up the new skill.
   - Fix is the checker's own remediation: `python3
     tools/dev/check-family-plugins.py --fix`. Output is exactly two
     changes — the `plugins/magpie-utilities/skills/report-framework-issue`
     symlink and the marketplace entry bumped from "4 skills" to
     "5 skills". No hand-written changes.
   
   ## Type of change
   
   - [x] CI / dev loop (`prek`, workflows, validators)
   
   ## Test plan
   
   - [x] `prek run --all-files` passes
   - [x] `python3 tools/dev/check-family-plugins.py` exits 1 on `main`
         before the change and 0 after regeneration
   - [x] `symlink-lint` and `check-family-plugins` hooks both green on the
         regenerated tree; the new symlink resolves
         (`plugins/magpie-utilities/skills/report-framework-issue →
         ../../../skills/report-framework-issue`, same relative shape as
         its siblings)
   
   ## RFC-AI-0004 compliance
   
   Generated-artefact sync only; no new mutations, network reach, or
   skill/tool prose. No principles touched.
   
   ## Linked issues
   
   Follow-up to [apache/magpie#922](https://github.com/apache/magpie/pull/922)
   and [apache/magpie#907](https://github.com/apache/magpie/pull/907).
   
   ## Notes for reviewers
   
   - Deliberately **not** included (stale but non-blocking, happy to do a
     follow-up or fold in here if preferred): the README utilities row
     still says "4 skills" and lists only the four original meta-skills,
     and `docs/setup/marketplaces.md` says "70 skills" in three places
     while `skills/` now holds 71. `docs/rfcs/RFC-AI-0007.md` also says
     "~3 MB across 70 skills" but reads as a historical snapshot, so I
     left it alone.
   


-- 
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(marketplace): sync magpie-utilities plugin with report-framework-issue skill [magpie]

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

onlyarnav commented on PR #1109:
URL: https://github.com/apache/magpie/pull/1109#issuecomment-5380389153

   Approving.
   I have considered the note for reviewer, and co-authored to update them.


-- 
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(marketplace): sync magpie-utilities plugin with report-framework-issue skill [magpie]

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

onlyarnav merged PR #1109:
URL: https://github.com/apache/magpie/pull/1109


-- 
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