BobSong-dev opened a new issue, #7949: URL: https://github.com/apache/shenyu/issues/7949
## Description Track the remaining Apache ShenYu OSPP Agent Gateway/MCP work against the mentor-approved `plan(1).md` (17-item plan, reviewed on 2026-10-21). Plan identifiers below are project priorities, not repository-wide severity labels. The project owner confirms P0-01 through P0-04 and P1-05 are development-complete. This does not assert that all associated PRs have merged: #7860, #7864 and #7921 were still open when checked. Reuse their accepted contracts and coordinate the integration baseline; do not rebuild those features or silently depend on unpublished changes. ## Remaining task list Child links and dependency details will be added here as the researched tasks are registered. No implementation or PR is part of creating this tracker. ## Existing ownership and reuse - P1-11: #7934 owns the usage ledger, versioned pricing and estimated cost attribution. #7911 / PR #7937 own the OpenAI Responses usage bug. Additional work must be limited to shared protocol-aware per-attempt metering and integration gaps, not another ledger or duplicate bug fix. - P1-14: #7702 / PR #7848 own opt-in token reservations and reconciliation. Reuse that foundation; only remaining identity-scoped, multidimensional token/cost policy and shadow/enforce integration belong to the follow-up. - P1-08: catalog freshness/recovery is separate from #7935 contract diffs, approval and pinning. Refresh generations are not stable tool-contract versions. - Existing resources PR #7669 is an independent earlier feature, not a newly scheduled P3 implementation. ## Conditional/deferred work - P2-15: no SDK migration implementation task until a selected protocol/client compatibility requirement or dependency-maintenance requirement is demonstrated. First assess MCP BOM, Spring AI and Java/Spring compatibility and public replacements for private reflection; an upgrade alone does not prove compatibility or remove reflection. Reprioritize before a dependent feature only when triggered. - P3-17: defer new resources work until a concrete file/knowledge-base use case identifies a gap beyond existing resources work. Do not recreate #7669 or assume its existence completes every future resources requirement. ## Tracking rules One coherent feature per implementation PR; explicit dependencies; no assignees set by this tracker. Keep authentication/authorization and base resource protection independent of shadow mode. Extend the existing interop regression matrix rather than creating a competing harness. No checkbox is completed merely because code is proposed or an issue is linked. Repository evidence baseline: master `87c22dde7be14c1c3755440a4d8b082a86d10a87`; open PRs are proposals until merged and verified. Original plan wording mentioning Spring AI is a reuse instruction where applicable, not a reason to replace the current native AI Proxy paths. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
