Add exact capability evidence for production parser calls in 7b reconciliation #1048

Closed
opened 2026-10-04 09:34:27 +00:00 by kayg · 1 comment
Owner

Reconciliation #867 merges production dev 6074f71d1 into 7b. The final regenerated-contract check reports:

perf-lint: FAIL; 140 violations; 19159 scoped exceptions

The unresolved calls are in production headingless Daily note parsing and Area-membership deduplication:

  • crates/plugins/notes/src/store.rs: 3 findings
  • crates/calternal-notes-core/src/dayfile.rs: 134 findings
  • crates/plugins/notes/src/tasks_store.rs: 3 findings

Command: bun run --cwd apps/web check. All findings are io.unresolved-call. Reconciliation kept exact-site hashes current and reduced the exception ratchet by 31. No new exception was added. Add exact capability evidence for these in-memory calls; keep unknown receiver methods unresolved. Do not add a general method-name allowlist or increase the exception ceiling. See docs/perf/reconcile-867.md.

Reconciliation #867 merges production dev 6074f71d1 into 7b. The final regenerated-contract check reports: ``` perf-lint: FAIL; 140 violations; 19159 scoped exceptions ``` The unresolved calls are in production headingless Daily note parsing and Area-membership deduplication: - `crates/plugins/notes/src/store.rs`: 3 findings - `crates/calternal-notes-core/src/dayfile.rs`: 134 findings - `crates/plugins/notes/src/tasks_store.rs`: 3 findings Command: `bun run --cwd apps/web check`. All findings are `io.unresolved-call`. Reconciliation kept exact-site hashes current and reduced the exception ratchet by 31. No new exception was added. Add exact capability evidence for these in-memory calls; keep unknown receiver methods unresolved. Do not add a general method-name allowlist or increase the exception ceiling. See `docs/perf/reconcile-867.md`.
Author
Owner

Round 4 fixes #1048 at the exact receiver-site evidence boundary. The 140 findings came from 85 in-memory call sites reached through several endpoints. Registry evidence pins both function and call syntax, requires enabled regression tests, and cannot apply to a different receiver, call or function. Guard regressions cover those cases and unsafe provider capabilities. The image paste host has one new raw-download boundary with a paired Blob-versus-JSON regression.

No new exception was added. Twenty obsolete entries were removed and the ratchet fell by 20; 29 existing entries retain their rule/file/symbol/limit with new source hashes after the production merge.

Verbatim results:

perf-lint: PASS; 0 violations; 19139 scoped exceptions
Ran 130 tests in 0.044s

OK
 Test Files  2 passed (2)
      Tests  10 passed (10)

The full web check next found two new local Retry focus rules from production image paste. They duplicate the shared ring at the same 2px offset and violate #658. Round 4 will remove those declarations so the shared token rules remain the sole owner.

Round 4 fixes #1048 at the exact receiver-site evidence boundary. The 140 findings came from 85 in-memory call sites reached through several endpoints. Registry evidence pins both function and call syntax, requires enabled regression tests, and cannot apply to a different receiver, call or function. Guard regressions cover those cases and unsafe provider capabilities. The image paste host has one new raw-download boundary with a paired Blob-versus-JSON regression. No new exception was added. Twenty obsolete entries were removed and the ratchet fell by 20; 29 existing entries retain their rule/file/symbol/limit with new source hashes after the production merge. Verbatim results: ```text perf-lint: PASS; 0 violations; 19139 scoped exceptions Ran 130 tests in 0.044s OK Test Files 2 passed (2) Tests 10 passed (10) ``` The full web check next found two new local Retry focus rules from production image paste. They duplicate the shared ring at the same 2px offset and violate #658. Round 4 will remove those declarations so the shared token rules remain the sole owner.
kayg closed this issue 2026-10-04 18:55:35 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#1048
No description provided.