|
|
6920bc6130
|
refactor(core): remove redundant @NotNull type-use annotation from async resource spec builder
|
2026-03-01 21:34:56 +08:00 |
|
|
|
23026d6dc8
|
refactor(framework): move RunningFlowContext from flow.entity to flow package
|
2026-03-01 21:31:04 +08:00 |
|
|
|
86b7e5c492
|
refactor(framework): rename agent.factory.module to agent.factory.component and update related imports
|
2026-02-21 17:57:29 +08:00 |
|
|
|
b2d44668da
|
refactor(framework): rename AgentConfigManager to AgentConfigLoader and update agent/core wiring
|
2026-02-21 16:51:59 +08:00 |
|
|
|
87c34cc699
|
refactor(modules): convert ActionScheduler to Standalone and simplify async execute signature
|
2026-02-20 17:29:26 +08:00 |
|
|
|
bbace28d7a
|
refactor(project): normalize formatting and reorder class members across modules
|
2026-02-20 17:22:54 +08:00 |
|
|
|
c47d2b2285
|
refactor(modules): refactor modules base class into AbstractAgentModule and remove unused @slf4j annotation
|
2026-02-20 17:17:49 +08:00 |
|
|
|
e00441faa8
|
refactor(framework): make AbstractAgentModule sealed with class-based module contracts and streamline ActivateModel model access
|
2026-02-20 16:12:35 +08:00 |
|
|
|
e57c03e213
|
refactor(framework): migrate module abstracts/ActivateModel to Kotlin and introduce shared model/context structures
|
2026-02-20 15:00:14 +08:00 |
|
|
|
c30ec35f85
|
refactor(framework): rename @AgentModule to @AgentRunningModule
|
2026-02-19 21:39:59 +08:00 |
|
|
|
c7f113b59a
|
refactor(framework): rename AgentRunningModule/SubModule to AbstractAgent* and migrate module inheritance usage
|
2026-02-19 15:04:30 +08:00 |
|
|
|
18b2bb8812
|
refactor(framework): reorganize Module abstracts location
|
2026-02-19 14:09:51 +08:00 |
|
|
|
7fccea5b91
|
chore(agent): add todo for PartnerOutputData
|
2026-02-19 14:07:39 +08:00 |
|
|
|
73ab40416d
|
refactor(Project): rename Partner-Api/Partner-Main modules to Partner-Framework/Partner-Core and update Maven dependencies
|
2026-02-19 10:39:21 +08:00 |
|
|
|
954095aa55
|
- 新建模块Partner-Api，推进Partner适配核心服务注册机制。
- 将原有的模块体系进一步区分，分离模型持有能力与调用能力，Model将有Module自身持有，可通过ActivateModel开启相应能力
|
2025-07-21 23:47:52 +08:00 |
|
|
|
dd10b00fb6
|
推进核心服务注册机制，并调整了Partner的模块结构
- 为了方便调试，将项目分为两个子模块，demo模块中进行新机制的开发工作，core模块为原来的Partner项目;
- 新增了多个注解，用于适配新的核心服务注册机制;
- 在`CapabilityRegisterFactory`中，将首先启动`statusCheck`，检查各个注解是否正常工作，包括以下内容:
- `CapabilityCore`核心服务与`Capability`接口是否匹配
- 核心服务中的`CapabilityMethod`是否与`Capability`接口中的方法匹配
- 是否存在待协调方法`ToCoordinatedMethod`以及对应的存在于`BaseCognationManager`子类实现中
|
2025-07-15 16:48:27 +08:00 |
|
