fix(deps): update rust crate toml to v1 by l3ocifer · Pull Request #97 · l3ocifer/frick-ironclaw

l3ocifer · 2026-05-31T00:21:33Z

This PR contains the following updates:

Package	Type	Update	Change
toml	dependencies	major	`0.8` → `1.1.2`

Release Notes

toml-rs/toml (toml)

Configuration

📅 Schedule: (in timezone America/New_York)

Branch creation
- Only on Sunday and Saturday (* * * * 0,6)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

l3ocifer · 2026-05-31T00:21:35Z

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --workspace
error: failed to parse manifest at `/tmp/renovate/repos/github/l3ocifer/frick-ironclaw/Cargo.toml`

Caused by:
  feature `default` includes `html-to-markdown` which is neither a dependency nor another feature

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/ironclaw_extensions/Cargo.toml --workspace
error: failed searching for potential workspace
package manifest: `/tmp/renovate/repos/github/l3ocifer/frick-ironclaw/crates/ironclaw_extensions/Cargo.toml`
invalid potential workspace manifest: `/tmp/renovate/repos/github/l3ocifer/frick-ironclaw/Cargo.toml`

help: to avoid searching for a non-existent workspace, add `[workspace]` to the package manifest

Caused by:
  failed to parse manifest at `/tmp/renovate/repos/github/l3ocifer/frick-ironclaw/Cargo.toml`

Caused by:
  feature `default` includes `html-to-markdown` which is neither a dependency nor another feature

l3ocifer · 2026-05-31T06:22:15Z

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

…ocabulary types (nearai#7758) * refactor(turns): delete the duplicate agent-turn metadata struct `AgentTurnProcessMetadata` was a 13-field strict subset of `AgentTurnProcessStateMetadata` serializing under the same durable `"agent_turn"` key. Two Rust types writing one key is the structural cause of the bug class fixed in nearai#7752: a row written by the subset type deserializes into the superset with serde defaults for the missing fields, which is exactly how `subagent_activation_provenance` was silently read back as `None` and left the autonomous-wake cap unable to fire. nearai#7752 fixed the instance; this removes the second writer so the class cannot recur through this path. Its only entry point was `TurnRunProcessExt::to_process_snapshot`, whose only caller was a test. Deleting the trait orphans `process_suspension_from_record` and `process_lease_from_record`, which die in the same commit. Three tests pinned real behavior through the deleted type and are re-pointed at the surviving one rather than dropped: - the `output_contract` serde-default pin (the survivor carries the identical attribute but nothing pinned it); - the five blocked-status -> suspension-kind mappings, now driven through `to_process_state_snapshot` (`process_suspension_from_state` is field-identical to the deleted twin and shares both underlying mapping fns); - the typed failure-metadata read-back in `ironclaw_turn_runner`, which was reading a superset payload through the subset type. Behavior unchanged. The deleted struct's fields are a strict subset of the survivor's, all serde-defaulted, under the same key, so removing the writer is invisible to every reader. Non-consumers confirmed: the journal-store migration builds a raw map, the rolling-compat contract uses its own frozen shape, and the suggestions observer reads untyped JSON. Evidence: cargo test -p ironclaw_turns --no-fail-fast 234 passed, 0 failed cargo test -p ironclaw_turn_runner --no-fail-fast 320 passed, 0 failed cargo test -p ironclaw_architecture_tests all green Both re-pointed tests were mutation-verified to fail when the behavior they pin is broken. Refs nearai#7755 (F2). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * refactor(subagent): collapse the two transposed spawn-mode enums `SubagentSpawnMode` (ironclaw_turn_runner) and `SpawnSubagentMode` (ironclaw_loop_host) had identical variant sets, identical derives, and the identical `#[serde(rename_all = "snake_case")]` attribute — transposed names for one concept, sitting on disjoint paths and reconciled by a hand-written identity mapping. This is the duplicate shape `.claude/rules/type-placement.md` names explicitly: different names, same variant set, invisible to name matching, and joined by a `From`-equivalent that never diverges. Per that rule a field-for-field identity mapping means the mirror is a violation — delete it and import the source type. The near-identical naming is separately flagged there as a grep/agent-discovery hazard, which is what made the pair survive this long. `ironclaw_loop_host` keeps the enum: it already owns `SubagentKindId` and the spawn wire contract, and `ironclaw_turn_runner` already imported from it, so no new dependency edge appears and the same-layer edge inventory is unchanged. Deleted: - SubagentSpawnMode (the turn_runner duplicate) - payload_spawn_mode, its identity converter - the aliased PayloadSpawnMode import Wire safety. Both enums carried the same serde attribute, so the emitted strings were already byte-identical; the collapse cannot move them. The mode is model-visible in `SpawnedChildRunPayload` and rides durable records (`AwaitedChildSetRecord.mode`, `SubagentThreadMetadata.mode`), so the strings are now pinned explicitly: a round-trip test covering *both* variants was added and proven green BEFORE the move, then re-run unchanged after it. The pre-existing payload test only ever asserted "background" and never round-tripped. Behavior unchanged. Evidence (full unfiltered runs): cargo test -p ironclaw_loop_host --no-fail-fast 980 passed, 0 failed cargo test -p ironclaw_turn_runner --no-fail-fast 321 passed, 0 failed cargo test -p ironclaw_turns --no-fail-fast 234 passed, 0 failed cargo test -p ironclaw_architecture_tests 42 suites, 0 failed Refs nearai#7755 (F1). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * docs(subagent): repoint two live design docs at the surviving spawn-mode type F1 deleted `SubagentSpawnMode`, leaving the name dangling in two design docs that are still live guidance. AGENTS.md requires searching docs and guidance for old paths after a move or rename; that search was missed in the F1 commit. - `thread-harness-design.md` is marked "Accepted design" and is the canonical tiebreaker for the await-edge harness; its `AwaitEdge` shape named a type that no longer exists. - `pr2-pr6-shape.md` is a one-day-old decision record for the *unimplemented* Slice 2. It instructed the future implementer to reach for `spawn_result.rs SubagentSpawnMode::Background` — a symbol and a location that are both now wrong. `phase-2-mechanisms.md` is deliberately left alone: it carries an explicit "Code citations are point-in-time (2026-05) and have drifted" banner, so it is a frozen historical snapshot rather than live guidance. Editing one symbol inside a block that is documented as drifted would falsely imply the rest is current. Docs only; no code change. Found by the design and coverage review lanes. Refs nearai#7755. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * fix(ci): re-anchor two coverage exemptions this branch's deletions moved `Fast deterministic checks` failed with: changed coverage gate failed: exemption #97 names a line beyond current EOF (125) Exemption #97 covers `steering_allowed_metadata_default` in `process_projection/metadata.rs`. It was pinned at lines 130-132, but the fn has actually lived at 184-186 on main for some time — the anchor was already stale and only passed because the file was long enough to clear the EOF check. F2 shrank the file from 186 to 125 lines, which pushed those numbers past EOF and surfaced it. Re-anchored to 123-125, the fn's real location now. Auditing the rest of this branch's changed files turned up a second, quieter one. F1 consolidated a three-line import in `await_edge/resolver.rs` into two, shifting every line below it up by one. Exemption #38 is written for the background spawn-mode gate-token statement; at line 2033 it now lands on a closing brace instead. It stayed within EOF so CI never complained, but a coverage exemption pointing at the wrong statement exempts the wrong line. Re-anchored to 2032. Both exemptions keep their original owner, reason, issue, and review_after — only the line anchors move, because only the lines moved. Verified with the exact CI command: python3 scripts/ci/reborn_changed_coverage.py \ --manifest tests/integration/changed-coverage-exemptions.toml \ --validate-manifest-only changed coverage manifest valid: 198 exemptions, line floor 90.0% Refs nearai#7755. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Henry Park <16583448+henrypark133@users.noreply.github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

fix(deps): update rust crate toml to v1

dbe0cda

l3ocifer added area:deps needs:owner-review renovate labels May 31, 2026

l3ocifer added area:deps renovate needs:owner-review labels May 31, 2026

github-actions Bot added the scope: dependencies label May 31, 2026

l3ocifer force-pushed the main branch from 6e371f4 to 326c208 Compare May 31, 2026 01:44

l3ocifer closed this May 31, 2026

l3ocifer deleted the renovate/toml-1.x branch May 31, 2026 01:45

Navigation Menu

fix(deps): update rust crate toml to v1 - #97

fix(deps): update rust crate toml to v1#97
l3ocifer wants to merge 1 commit into
mainfrom
renovate/toml-1.x

l3ocifer commented May 31, 2026

Uh oh!

l3ocifer commented May 31, 2026

Uh oh!

l3ocifer commented May 31, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

l3ocifer commented May 31, 2026

Release Notes

Configuration

Uh oh!

l3ocifer commented May 31, 2026

⚠️ Artifact update problem

File name: Cargo.lock

File name: Cargo.lock

Uh oh!

l3ocifer commented May 31, 2026

Renovate Ignore Notification

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant