build(deps-dev): bump jest from 30.2.0 to 30.3.0 in /backend#54
Merged
Conversation
Bumps [jest](https://github.com/jestjs/jest/tree/HEAD/packages/jest) from 30.2.0 to 30.3.0. - [Release notes](https://github.com/jestjs/jest/releases) - [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md) - [Commits](https://github.com/jestjs/jest/commits/v30.3.0/packages/jest) --- updated-dependencies: - dependency-name: jest dependency-version: 30.3.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
mr-torto
pushed a commit
to mr-torto/SmartPerfetto
that referenced
this pull request
May 8, 2026
Replace the monolithic "any code change → trace regression" rule with an explicit four-tier policy that distinguishes work that genuinely exercises agent behavior from contract / type-only and CRUD-only changes that don't: - Contract / type-only (`backend/src/types/sparkContracts.ts` etc.) → `npx tsc --noEmit` + the sparkContracts.test.ts case for that contract. - CRUD-only service (file IO, no agent path touched) → that service's own `__tests__/<name>.test.ts`. - Touches mcp / memory / report / agent runtime → `npm run test:scene-trace-regression` (the existing 6-trace gate). - PR landing → `npm run verify:pr` (strict full gate, unchanged). The new policy is inlined consistently in all 7 rule documents — keeping fresh clones self-contained — and the wording is identical across files so future drift is easy to spot. Files touched: CLAUDE.md, AGENTS.md, docs/development/testing.md, README.md, README.zh-CN.md, CONTRIBUTING.md, docs/getting-started/quick-start.md. Motivation: subsequent Spark contract scaffold commits (Gracker#41 / Gracker#44 / Gracker#50 / Gracker#54 / Gracker#55) only add types to sparkContracts.ts and add unit tests. Running the full 6-trace regression on each adds minutes per commit without exercising any code path the contract touches. The tiered policy keeps the strict gate where it earns its keep (anything wired into the agent runtime, plus PR landing) while letting type-only work finish in seconds. The trace regression command itself is unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
mr-torto
pushed a commit
to mr-torto/SmartPerfetto
that referenced
this pull request
May 8, 2026
Land Plan 44 (Spark Gracker#94, Gracker#95) — project / world memory plus the feedback → case → skill draft pipeline. Critical invariant: this contract does NOT modify the existing session-scope `analysisPatternMemory.ts`. Plan 44 introduces an independent project + world store at runtime (`backend/src/agentv3/projectMemory.ts`, landed in D-phase). The existing 200-entry session store, weighted Jaccard matching, and supersede integration stay untouched. Types added to `backend/src/types/sparkContracts.ts`: - `ProjectMemoryStatus` — 5-state status machine inlined to keep `backend/src/types/` independent of `backend/src/agentv3/`. Mirrors agentv3's PatternStatus including `disputed_late`. Doc note flags that the two unions must stay in sync; if agentv3 changes, mirror the change here. - `ProjectMemoryEntry` — one entry. Carries optional `promotionPolicy`; the Plan 44 service layer (`projectMemory.saveProjectMemoryEntry`) enforces that a `'world'`-scope entry MUST have a policy. Schema itself keeps it optional so older snapshots remain readable. - `FeedbackPipelineEntry` — feedback pipeline state. Uses the shared `CaseRef` from C0 base types so this contract does NOT depend on Plan 54's CaseNode shape, breaking the Gracker#44 ↔ Gracker#54 schema cycle that Codex flagged in round 1. - `MemoryRagSelfImprovementContract` — service surface bundling entries + pipeline + recent RAG retrievals. Storage location for project + world entries: `backend/logs/analysis_project_memory.json` with shape `{entries: ProjectMemoryEntry[], promotionAudit: ...}`. Audit log schema is finalized in §4.3 of the design doc. Five new test cases in `__tests__/sparkContracts.test.ts` cover: - ProjectMemoryStatus matches the 5-state machine, no `auto_inferred` - project entry can omit promotionPolicy - world entry carries promotionPolicy with reviewer for audit - FeedbackPipelineEntry uses CaseRef shape, not CaseNode - contract bundles entries + pipeline + recent retrievals Test count: 55 (was 50). Test tier: contract / type-only. `npx tsc --noEmit` clean, sparkContracts.test.ts passes 55/55. Trace regression intentionally not run per the tiered policy in commit d8529e1. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps jest from 30.2.0 to 30.3.0.
Release notes
Sourced from jest's releases.
Changelog
Sourced from jest's changelog.
Commits
efb59c2v30.3.096c53d3feat(jest-config): adddefineConfigandmergeConfigfunctions (#15844)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)