Skip to content

T5: hermetic smoke hypignore_capture_drop#210

Merged
philcunliffe merged 1 commit into
integration/hypignore-usage-policyfrom
task/hypignore-usage-policy/T5
Jun 30, 2026
Merged

T5: hermetic smoke hypignore_capture_drop#210
philcunliffe merged 1 commit into
integration/hypignore-usage-policyfrom
task/hypignore-usage-policy/T5

Conversation

@philcunliffe

Copy link
Copy Markdown
Contributor

Implements task T5 of hypignore-usage-policy.

Hermetic smoke hypaware-core/smoke/flows/hypignore_capture_drop.js: drives one Claude exchange from a .hypignore'd cwd and one from a clean cwd through the daemon, then asserts only the clean row lands in the cache and a usage_policy_drop event is emitted. Stable smoke_name/smoke_step per phase (log-driven). Registered in the README smoke battery (the flow index).

Checks: npm test (1521 pass), npm run typecheck, npm run lint, and npm run smoke -- hypignore_capture_drop all green.

Task-Id: T5

🤖 Generated with Claude Code

…P 0053 T5)

Hermetic smoke that drives one Claude exchange from a `.hypignore`'d cwd and
one from a clean cwd through the daemon (ai-gateway + claude), then asserts:

- only the clean session's rows land in `ai_gateway_messages` (no ignored cwd,
  no ignored session id), proving R1;
- the gateway returned 200 for the ignored exchange and its `aigw.exchange`
  log recorded `rows_written = 0`, proving R2 (live call untouched);
- the claude projector emitted a `usage_policy_drop` event naming the governing
  `.hypignore`.

Each phase runs under a stable `smoke_name`/`smoke_step` root span so a failure
names the broken step. Registered in the README smoke battery (the flow index).

@ref LLP 0049#requirements [tests]
@ref LLP 0050 [tests]
@ref LLP 0053#tasks

Task-Id: T5

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@philcunliffe philcunliffe merged commit 7a201bf into integration/hypignore-usage-policy Jun 30, 2026
6 checks passed
@philcunliffe philcunliffe deleted the task/hypignore-usage-policy/T5 branch June 30, 2026 04:02
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