feature/assertions tools support FIRE 1094

[drorIvry]

• Feature - new apis (Feature - new apis #28)
• feat: policy tools

Description of change

Pull-Request Checklist

• Code is up-to-date with the main branch
• npm run lint passes with this change
• npm run test passes with this change
• This pull request links relevant issues as Fixes #0000
• There are new or updated unit tests validating the change
• Documentation has been updated to reflect this change
• The new commits follow conventions outlined in the conventional commit spec

Summary by CodeRabbit

• New Features

  • Enhanced policy evaluation with new configuration options: ability to include or exclude tools from policy evaluation, control assertion modes, enable multi-turn policy evaluation, and specify policy targets.

• Chores

  • Version bumped to 1.8.0.
  • Added test coverage for new policy configuration features.

[coderabbitai]

Walkthrough

Version bump from 1.7.0 to 1.8.0 with addition of policyIncludeTools field to evaluation request schemas, request wiring in both backward-compatibility and converter paths, and corresponding test coverage.

Changes

Cohort / File(s)	Summary
Version Update package.json	Bumped version from 1.7.0 to 1.8.0.
Schema Definitions src/types.ts	Added policyIncludeTools boolean field with default false to both EvaluationRequestV2Schema and EvaluationProxyAPIRequestSchema.
Request Wiring src/index.ts	Mapped policyIncludeTools from request objects to API request payloads in both backward-compatibility and converter paths, propagating the field to evaluation request bodies.
Test Coverage test/index.spec.ts	Added test suite "policy_include_tools field" with tests verifying that policy_include_tools: true appears in API request bodies for both direct and framework evaluation modes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Hotfix | New evaluations-api schema fix #21: Both PRs modify evaluation request schema and wiring by adding policy/assertion/mode-related fields to src/types.ts and src/index.ts.
• Feature - new apis #28: Both PRs extend evaluation request payload wiring and types with policy-related fields in src/index.ts and src/types.ts.

Suggested reviewers

• amos-qualifire
• yuval-qf
• osher-qualifire

Poem

🐰 Tools and policies unite,
Schemas bloom with new delight,
Version springs from one-point-seven,
Tests confirm the feature's heaven!
Include them all, in tools we trust ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The PR title 'feature/assertions tools support FIRE 1094' is partially related to the changeset. The title mentions 'assertions tools support' but the actual changes focus on adding 'policyIncludeTools' field support across schemas, types, and tests, which is broader than just assertions. The title is somewhat vague and doesn't clearly reflect the primary technical change.	Revise the title to more specifically describe the main change, such as 'Add policyIncludeTools field support to evaluation requests' or 'Support policy tool inclusion in evaluation API'. This would better reflect the actual implementation details.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/assertions-tools-support-FIRE-1094

---

No actionable comments were generated in the recent review. 🎉

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[yuval-qf]

LGTM