TVO-CONFLICT-018: Line-op capture missed an eligible file

If this error reveals a permission or cryptography flaw, do not post it — follow coordinated disclosure. Do not report security vulnerabilities here. This board is public and operated by a third-party vendor. Read https://tovio.dev/security and use the private channel it names. Never paste repository contents, file paths, diffs, tokens, keys, or other people's data — describe the behaviour instead.

Why it happened

In the catalog's worked example, TOVIO explains it like this. Names and values in it are illustrative.

[line_ops] strict = true requires every eligible changed file to record its line-ops, and 2 did not. … Nothing was committed: ~ src/nutrition/plan.ts (seal) ~ src/nutrition/ui.tsx (encode)

How to fix it

1. Check the path still resolves a reader to seal to: tovio access check src/nutrition/plan.ts
2. Retry the commit once the cause is cleared
3. Or set strict = false under [line_ops] in .tovio/config.toml to return to the advisory default (capture absence then warns, never blocks)

What TOVIO prints

The catalog's example of what TOVIO prints for this code in a terminal. Names, paths and counts in it are illustrative, and the command exits with status 1.

✗ Cannot commit: 2 changed file(s) recorded no line-ops

  `[line_ops] strict = true` requires every eligible changed file to record its line-ops, and 2 did not.
  They are not binary, not oversized, not unchanged and not a materialized conflict, so the chained-merge
  guarantee would quietly stop holding for them and a later land would re-diff instead of composing. Nothing
  was committed:
    ~ src/nutrition/plan.ts  (seal)
    ~ src/nutrition/ui.tsx  (encode)

  Check the path still resolves a reader to seal to:
    tovio access check src/nutrition/plan.ts
  Retry the commit once the cause is cleared
  Or set `strict = false` under `[line_ops]` in .tovio/config.toml to return to the advisory default
  (capture absence then warns, never blocks)

  [TVO-CONFLICT-018]

What to read

• Error reference — the three-part message standard (what happened, why, what to do next), the exit-code classes, the --json shape, and the everyday codes. It is a curated subset, so it may not name this one: TVO-CONFLICT-018 is in the CONFLICT area and carries the same three-part message either way.
• Troubleshooting — the diagnostic commands and recovery paths behind the most common failures.

Still stuck, or is the message wrong?

Report it. The link carries only this code and the surface; describe the behaviour in your own words and never paste secrets, capability tokens, session strings, or private repository data.

Report this error

All error codes