chore(organisation): place tests/chunking-regex-hoist.test.ts under source-intake

Merged
BI
1mo ago
+1-0

User description

Summary

  • Places tests/chunking-regex-hoist.test.ts, the one file check:organisation reported as unplaced, under source-intake. The test exercises src/lib/chunking.ts, which source-intake.json already owns explicitly, along with tests/chunking.test.ts and tests/property-chunking.test.ts.
  • This adds one sorted entry to docs/organisation/systems/source-intake.json. No organisation or ownership check changed.

Areas touched: Knowledge and records

Verification

  • Checks run: check:organisation went from 0 not yet placed, 1 unplaced (warning: tests/chunking-regex-hoist.test.ts: is not placed in any area yet) to 10436 placed, 4 shared, 1 ignored, 0 not yet placed, 0 unplaced. All Static PR checks steps pass locally, including check:knip. vitest run tests/chunking-regex-hoist.test.ts tests/maintain-docs-system.test.ts tests/organisation-*.test.ts: 428 passed.

Risk and rollout

  • Risk: low. This is ownership metadata only.
  • Rollback: revert the commit.
  • Provider or production effects: None

Notes

Summary by cubic

Places tests/chunking-regex-hoist.test.ts under source-intake in the organisation metadata, resolving the last check:organisation "unplaced" warning. The test covers src/lib/chunking.ts, which source-intake already owns alongside tests/chunking.test.ts and tests/property-chunking.test.ts; no ownership rules changed.

CodeAnt-AI Description

Register the chunking regex-hoist test under source-intake ownership

What Changed

  • Source-intake ownership records now include the chunking regex-hoist test, so organisation checks recognize it as assigned.

Impact

✅ No unassigned chunking regex-hoist test

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.