chore(deps): Bump toml from 1.1.6+spec-1.1.0 to 1.1.8+spec-1.1.0

[dependabot]

Bumps toml from 1.1.6+spec-1.1.0 to 1.1.8+spec-1.1.0.

Commits

• ceac6e4 chore: Release
• 0fe9e93 docs: Update changelog
• e3a64aa fix(display): Ensure all keys are encoded (#1245)
• 76484d0 fix(display): Ensure all keys are encoded
• 711b1ba refactor(display): Clarify that we are working with encoded keys
• 4f73ebd test(display): Reproduce the key bug
• 6c6a5cd fix(parser): Remove risk of unsoundness with synthetic parser events and 'uns...
• 9c5e95d fix(parser): Remove risk of unsoundness with synthetic parser events and 'uns...
• 4d45944 perf(parser): Remove no-op code (#1243)
• 189c91c perf(parser): Remove no-op code
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies, rust. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

∵ causari · AI code survival

277 commits analyzed (git metadata only, retroactive, no setup).

AI-tagged (metadata matched): 82.0% line-weighted (5142 of 6267 lines still at HEAD, 14 commits) · 82.0% capped · median 92.5%

Of the lines introduced by metadata-matched commits, this percentage is the share git blame -w -M -C still attributes to those commits. It is not the share of the repository and it is not a quality score. Metadata matched does not prove who wrote each line. UNKNOWN and untagged are commits with no such signal; they are not a finding that a human wrote them.

Age-matched gap: +3.4 percentage points (AI-tagged 84.6% minus untagged 81.2% in the matched age windows). Positive means the metadata-matched lines have the higher line-weighted survival in those windows, over 1 matched age window holding 75% of the AI-tagged lines. Lines outside those windows are not in this gap.

Same repository, untagged lines: 192361 of 241457 still at HEAD (79.7% line-weighted, 263 commits).

Line age	AI-tagged	Untagged
0-30 d	84.6% (13 commits)	81.2% (182 commits)
30-90 d	—	63.0% (41 commits)
90-180 d	74.3% (1 commit)	63.9% (40 commits)

Agent	Commits	Introduced	Survived	Line-weighted	Capped	Median
cursor	14	6267	5142	82.0%	82.0%	92.5%

_{PROBABLE = heuristic. Counts lines from AI-tagged commits still attributed to them by git blame -w -M -C; inline completions leave no git trace and are not measured. Capped: each commit weighs at most min(p95 of per-commit introduced lines, 10000 lines); median: median of per-commit rates. Untagged = commits with no AI signal (human, inline-completed and untagged-agent code alike); age = commit date to HEAD date. absent means no introduced lines are included in the measurement (JSON null), not a measured zero and not a claim that the commits introduced nothing. An unavailable age-matched gap is not a gap of zero. Method v4: causari.dev/method. --json stores the commit, method, blame flags and counts. It does not store refs/notes/ai. The JSON field is still verified: metadata matched, not authorship proved.}

Read the age-matched gap as the comparison. An agent line marked below floor is not comparable. Meeting the floor is not a reliability guarantee.

Export: re audit <target> --json (the counts and commit 0e2648ae01f75898dbc64c13411844dcec87e5ef), --summary for this Markdown, --seal to sign those JSON bytes for that commit and method v4. --badge and --card write SVGs. re report is the local ledger, not this audit.

The export stores the counts, commit 0e2648ae01f75898dbc64c13411844dcec87e5ef, method v4, blame -w -M -C, and the coverage flags. It does not store refs/notes/ai. That ref is not part of the commit; adding or removing it can change the counts while the stored SHA stays the same. A repository that has moved has a different commit, and this export does not reproduce it.

Sealed: cs_2026_5J4V7TZQ4GW7NVIX3IBPFHOTUQ (crovia.seal.v1) over this audit of 0e2648ae01f7, written to causari-audit.seal.json. Verify offline with re seal verify causari-audit.seal.json or at https://causari.dev/verify — the seal proves these exact numbers were signed for this commit, not that they are true.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	causari	32088e4	Commit Preview URL Branch Preview URL	Oct 13 2026, 01:43 PM