@gencode/agents 0.16.4 → 0.17.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +20 -0
- package/dist/index.d.ts +6 -0
- package/dist/index.js +119 -116
- package/package.json +3 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,25 @@
|
|
|
1
1
|
# @gencode/agents
|
|
2
2
|
|
|
3
|
+
## 0.17.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- b352a92: Add Phase 2 core memory lifecycle wiring for recall, capture, and compaction recall. All features remain default-off until explicitly enabled via `memory.core` structured config. Retrieval regression fixture gates recall quality before default enablement.
|
|
8
|
+
- b352a92: Add Phase 3 Knowledge Controller integration as an optional core memory fallback layer. CLI parses `AIMAX_MEMORY_KC_*` env vars into structured `memory.core.knowledgeController` config; agents dynamically import KC only when enabled with `searchMode=fallback` and local recall is empty or weak. KC failures emit diagnostics without blocking agent runtime creation.
|
|
9
|
+
|
|
10
|
+
### Patch Changes
|
|
11
|
+
|
|
12
|
+
- b352a92: Default local memory is now built into the core: daily entries go to `.aimax/memory/YYYY-MM-DD.md`, structured `MEMORY.md` updates merge by section, and no plugin is required for the default provider path. Optional core capabilities—recall, capture, compaction recall, and Knowledge Controller—are configured via `memory.core` and remain off unless explicitly enabled (`memory.core.*.enabled`). CLI parses `AIMAX_MEMORY_KC_*` into structured `memory.core.knowledgeController` for agents. The `aimax-memory-plugin` continues to provide Mem0 Cloud, Mem0 OSS, and third-party memory provider overrides when selected through `plugins.slots.memory` in `plugins.json` or a file passed with `--plugins-config`, with plugin discovery configured through `plugins.load.paths`.
|
|
13
|
+
- b352a92: The built-in memory provider now handles recent memory writes without requiring a plugin: daily entries are appended to `.aimax/memory/YYYY-MM-DD.md`, session entries use `.aimax/memory/session-<sessionId>.md`, and structured `MEMORY.md` updates replace matching sections while preserving unrelated sections. This keeps the default CLI memory path aligned with the local memory layout users already configure under `.aimax`.
|
|
14
|
+
- b352a92: Require the public `goal` completion tool to submit a per-task acceptance report. A complete goal now needs `completedTasks` entries covering every required task and required acceptance criterion with evidence summaries and sources; AIMax records those entries as manual evidence before marking the workflow complete.
|
|
15
|
+
|
|
16
|
+
Goal continuation context now includes the required task and acceptance-criterion ids needed to build that completion report. Calls that omit required summaries, tasks, criteria, or evidence sources are rejected with structured errors such as `missing_summary`, `missing_completed_tasks`, `missing_required_completed_task`, `missing_required_acceptance_evidence`, `blocked_tasks_remain`, `unknown_completed_task`, `unknown_acceptance_criterion`, `missing_evidence_summary`, `missing_evidence_source`, `workflow_not_initialized`, or `workflow_corrupt`.
|
|
17
|
+
|
|
18
|
+
- b352a92: `aimax run` now releases built-in memory index watchers and timers at the end of each agent run. This keeps the default core memory provider path from holding the Node.js process open after the final session output has been written, while preserving the existing `.aimax/MEMORY.md` and `.aimax/memory/YYYY-MM-DD.md` storage layout.
|
|
19
|
+
- 02c5263: Skills can now request approval for side-effectful shell work without writing a plugin. Skill authors can declare validated actions in `actions.yml` next to `SKILL.md` and invoke them through `skill_action_run`, or ask for one-off command approval with `guarded_exec`. Invalid action configuration, invalid inputs, workspace escapes, and commands changed after approval fail before any script runs.
|
|
20
|
+
- Updated dependencies [b352a92]
|
|
21
|
+
- @gencode/shared@0.5.0
|
|
22
|
+
|
|
3
23
|
## 0.16.4
|
|
4
24
|
|
|
5
25
|
### Patch Changes
|
package/dist/index.d.ts
CHANGED
|
@@ -1586,6 +1586,12 @@ type GoalWorkflowPromptContext = {
|
|
|
1586
1586
|
blockedReason: string | null;
|
|
1587
1587
|
taskBlockedReason: string | null;
|
|
1588
1588
|
acceptanceCriteria: GoalWorkflowAcceptanceCriterion[];
|
|
1589
|
+
requiredTasks: Array<{
|
|
1590
|
+
taskId: string;
|
|
1591
|
+
title: string;
|
|
1592
|
+
status: GoalWorkflowTaskStatus;
|
|
1593
|
+
acceptanceCriteria: GoalWorkflowAcceptanceCriterion[];
|
|
1594
|
+
}>;
|
|
1589
1595
|
openQuestions: string[];
|
|
1590
1596
|
};
|
|
1591
1597
|
declare const FIRST_TURN_GOAL_WORKFLOW_INTRO = "The user just set a thread goal. Acknowledge it implicitly, then work on the current workflow task below.";
|