@ouro.bot/cli 0.1.0-alpha.267 → 0.1.0-alpha.268
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.json +6 -0
- package/dist/heart/identity.js +8 -0
- package/package.json +1 -1
package/changelog.json
CHANGED
|
@@ -1,6 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"_note": "This changelog is maintained as part of the PR/version-bump workflow. Agent-curated, not auto-generated. Agents read this file directly via read_file to understand what changed between versions.",
|
|
3
3
|
"versions": [
|
|
4
|
+
{
|
|
5
|
+
"version": "0.1.0-alpha.268",
|
|
6
|
+
"changes": [
|
|
7
|
+
"fix(identity): `loadAgentConfig` now preserves the `sync` block from agent.json. The hand-rolled object literal that constructs the typed `AgentConfig` was missing `sync` from its field list, so `agentConfig.sync` was always `undefined`, `getSyncConfig()` always returned `enabled: false`, and the entire sync code path (`preTurnPull` / `postTurnPush` in `pipeline.ts`) was dead from the moment the field was added to the type. The bug hid for weeks because `ouro status` reads `agent.json` directly via `listBundleSyncRows`, not through `loadAgentConfig` — so the per-agent Git Sync display correctly showed `enabled origin → ...` while sync did literally nothing. Slugger accumulated 5+ days of dirty files and zero `sync: post-turn update` commits before this surfaced. Also adds 3 regression tests asserting the sync block round-trips through `loadAgentConfig` (full block, partial block, missing block). The first two would have caught the original bug; without them future field additions to `AgentConfig` could repeat the pattern."
|
|
8
|
+
]
|
|
9
|
+
},
|
|
4
10
|
{
|
|
5
11
|
"version": "0.1.0-alpha.267",
|
|
6
12
|
"changes": [
|
package/dist/heart/identity.js
CHANGED
|
@@ -416,6 +416,14 @@ function loadAgentConfig() {
|
|
|
416
416
|
mcpServers: parsed.mcpServers,
|
|
417
417
|
phrases: parsed.phrases,
|
|
418
418
|
vault: parsed.vault,
|
|
419
|
+
// The sync block was missing from this hand-rolled object literal since
|
|
420
|
+
// it was added to AgentConfig. Result: `getSyncConfig()` always read
|
|
421
|
+
// `agentConfig.sync?.enabled ?? false` and always saw undefined, so the
|
|
422
|
+
// entire sync code path (preTurnPull / postTurnPush in pipeline.ts) was
|
|
423
|
+
// dead. The `ouro status` per-agent Git Sync display kept reporting
|
|
424
|
+
// "enabled" because it reads agent.json directly via `listBundleSyncRows`,
|
|
425
|
+
// not through loadAgentConfig — so the bug hid in plain sight for weeks.
|
|
426
|
+
sync: parsed.sync,
|
|
419
427
|
};
|
|
420
428
|
(0, runtime_1.emitNervesEvent)({
|
|
421
429
|
event: "identity.resolve",
|