feat(a2a): publish remote agent catalog snapshots

[openjiuwen-sync-bot]

Paired: GitHub #84 ↔ GitCode !146

变更内容

/kind feature

• 为远端 A2A Agent Card 注册表增加线程安全的全量目录快照和单调递增版本号。
• Agent Card 注册后发布目录变更事件，供 runtime 扩展层按最新完整目录重建意图项。
• 统一由 A2A 自动配置创建注册表实例，确保目录变更事件从实际运行实例发出。
• 补充并发更新、快照不可变性、事件发布和自动配置测试。

跨仓边界

• 本 PR 提供 runtime 的动态 Agent Card 目录能力。
• DeepAgent 意图套件、Spring 装配和端到端示例由 agent-solution 的配套 PR 实现。
• 不改变 DeepAgent 原有 invoke() 调用路径，也不改变现有逐 Agent Card 工具注入的默认行为。

验证结果

• mvn -pl :agent-service-app -am test：405 个测试通过
• mvn -pl service/agent-service-adapters/agent-service-adapters-agentcore test：151 个测试通过，8 个跳过
• service/agent-service-demo/example/a2a 四 Agent 真实模型端到端回归通过
• git diff upstream/develop --check

Self-checklist

• 设计：对应 L2 方案已经完成评审和拆分。
• 测试：新增目录行为已有单元测试覆盖。
• 验证：已完成现有 A2A 示例回归。
• 接口：新增目录快照和事件类型，不改变既有 Agent 调用方式。
• 文档：配套 L2 文档已提交文档仓。

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

xiaoming-2026 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[openjiuwen-collaboration-bot]

head_sha: d9277f59aad382275c929925efaf77440e0c9db2

Merge Verification Failed

@xiaoming-2026, this pr is not mergeable and the reasons are below:

Not Enough Labels

• the pull request needs 1 approved labels, but now gets 0.
• the pull request needs 1 ci-successful labels, but now gets 0.
• the pull request needs 2 lgtm labels, but now gets 0.

Label Usage Tips

• approved: Agree to merge the pull request. This can be accomplished by commenting /approve
• lgtm: The code has been reviewed. This can be accomplished by commenting /lgtm

[openjiuwen-collaboration-bot]

head_sha: d9277f59aad382275c929925efaf77440e0c9db2

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: 124a86b7196e9c1802e270edd40f05864d924e46

Merge Verification Failed

@xiaoming-2026, this pr is not mergeable and the reasons are below:

Label BlockList

• the ci-failed label(s) caused the pull request to be unable to merge.

Not Enough Labels

• the pull request needs 1 approved labels, but now gets 0.
• the pull request needs 1 ci-successful labels, but now gets 0.
• the pull request needs 2 lgtm labels, but now gets 0.

Label Usage Tips

• approved: Agree to merge the pull request. This can be accomplished by commenting /approve
• lgtm: The code has been reviewed. This can be accomplished by commenting /lgtm

[openjiuwen-collaboration-bot]

head_sha: 124a86b7196e9c1802e270edd40f05864d924e46

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: 02e56e19a4e45917612db5c43f618a1dc6782439

Merge Verification Failed

@xiaoming-2026, this pr is not mergeable and the reasons are below:

Label BlockList

• the ci-failed label(s) caused the pull request to be unable to merge.

Not Enough Labels

• the pull request needs 1 approved labels, but now gets 0.
• the pull request needs 1 ci-successful labels, but now gets 0.
• the pull request needs 2 lgtm labels, but now gets 0.

Label Usage Tips

• approved: Agree to merge the pull request. This can be accomplished by commenting /approve
• lgtm: The code has been reviewed. This can be accomplished by commenting /lgtm

[openjiuwen-collaboration-bot]

head_sha: 02e56e19a4e45917612db5c43f618a1dc6782439

TASK	STATUS	DETAILS
CodeCheck	✅SUCCESS	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: f5c6b3be61e95b26e505ce2ce0c44e54530299b4

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: e9651be821fa13e46d95957db9ee439d50d9827f

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: 1de1ff077e3f6a6ce7c3bde27f33c4d3c394d30f

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: 62a1787d5c50dbd0e897132772590cddd6e4418a

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: 7d1f0e3ca4cd7d9ad525cb42e09c609074e23de4

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: 3e1957f0377c6bcec9cca3c75bd4e063af7de71c

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: b70ea32c02d88ddc3705bd10be96ea3f439da5b9

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab

[openjiuwen-collaboration-bot]

head_sha: e9a91b5066a0f3c9b33915940ed05a7c84127558

TASK	STATUS	DETAILS
CodeCheck	❌FAILED	Click here
AntiPoison	✅SUCCESS	Click here
Software Composition Analysis	✅SUCCESS	Click here
Maven Build	✅SUCCESS	See CHECK tab