Skip to content

feat(dev)!: same-entity-schema and same-error-reason fail the family audit - #574

Merged
leemour merged 1 commit into
mainfrom
fix/family-audit-fails
Nov 13, 2026
Merged

leemour merged 1 commit into
mainfrom
fix/family-audit-fails

Conversation

@leemour

@leemour leemour commented Nov 13, 2026

Copy link
Copy Markdown
Member

Task

Owner ruling NEED-2578 A: the family audit rules same-entity-schema and same-error-reason must fail, not warn. Ships in 0.99.0 with #573.

Why

0.98.0 printed their findings as warnings, so a new divergence between CLIs went unnoticed.

What

  • cli-dev audit --family fails on new findings of both rules.
  • Today's 11 differences are declared as parity-group differences with review_after: 2026-11-27 and a reason each, so no published CLI turns red today:
    • messengers: entity contact_context, entity contact_preparation, entity linked_person (max, tg, wa)
    • gcal-shared: entity api_method, entity scheduled_job, entity hit, entity deal, entity lead, entity product, reason ai.address-refused=model.address-refused, reason profile.unknown: code
  • A difference of these two rules names no CLI list. Which CLIs share an entity or reason changes with each publish (zm joined the address finding within an hour), so a listed target would go stale. The review_after date retires it instead of a stale check.
  • oauth.missing vs session.missing is not a finding today, so it has no row.

Testing

  • Family audit from bitrix24-cli main (cli-core 0.648.0, throwaway HOME, DBUS_SESSION_BUS_ADDRESS=disabled: on the CLI runs): exit 0, 0 new findings for any of the 9 CLIs.
  • New test: an unlisted difference accepts its finding, and another entity still blocks.
  • vitest run (68 files, 1117 tests), typecheck, biome, docs:check, docs:lint.

🤖 Generated with Claude Code

…audit

Owner ruling NEED-2578 A: the two rules the family audit measured first in 0.98.0 printed warnings;
now they fail like every other rule.

So that no published CLI turns red today, the 11 differences measured on 2026-11-13 are declared as
parity-group differences with review_after 2026-11-27 and a reason each (3 in messengers, 8 in
gcal-shared, under the budget of 10). A difference of these two rules names no CLI list (`entity hit`,
`reason profile.unknown: code`): which CLIs share an entity or reason changes with each release (zm
joined the address-refused finding within an hour), so a listed target would go stale on every
publish. Its review_after retires it, not a stale check.

Checked: the family audit from bitrix24-cli main (throwaway HOME, DBUS disabled on the CLI runs)
exits 0 with 0 new findings for any of the 9 CLIs; a test shows an unlisted difference accepts its
finding and a different entity still blocks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit fb51401 into main Nov 13, 2026
10 checks passed
@leemour
leemour deleted the fix/family-audit-fails branch November 13, 2026 01:24
@leemour leemour mentioned this pull request Nov 13, 2026
leemour added a commit that referenced this pull request Nov 13, 2026
Dates the changelog and raises the version for #573 and #574. Only
package.json and the CHANGELOG heading change.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant