Skip to content

fix: use shared auto-compact threshold constants - #1193

Open
DeepamJha wants to merge 1 commit into
Nano-Collective:mainfrom
DeepamJha:fix/shared-auto-compact-threshold
Open

fix: use shared auto-compact threshold constants#1193
DeepamJha wants to merge 1 commit into
Nano-Collective:mainfrom
DeepamJha:fix/shared-auto-compact-threshold

Conversation

@DeepamJha

Copy link
Copy Markdown
Contributor

Summary

  • Use COMPRESSION_CONSTANTS as the single source of truth for auto-compact threshold clamping.
  • Update boundary tests to derive expected values from the shared constants.
  • Prevent threshold ranges from drifting between implementations.

Closes #1137

Validation

  • Focused AVA suite: 41 passing
  • Lint: passed
  • Format: passed
  • pnpm test:all: blocked by intermittent Corepack/pnpm signing-key verification.

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

No changeset found

This PR does not add a changeset, so it will not appear in the changelog or trigger a release.

If the change is user-facing, add one:

pnpm changeset

Pick a bump (patch / minor / major) and write the changelog entry in our usual voice ("Added X... Thanks to @you. Closes #123."), then commit the generated .changeset/*.md file.

If this PR is docs-only or a chore that needs no release note, you can ignore this - or run pnpm changeset --empty to record that intentionally.

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.

[Bug] setAutoCompactThreshold clamp range defined in two places

1 participant