feat: flag mutual Compose dependencies

[Joncallim]

Summary

• derive a deterministic, read-only advisory when exactly one fresh Docker Compose dependency exists in each direction between two unique containers
• fail closed for malformed, stale, timed-out, duplicate, colliding, mock, or mismatched evidence
• regenerate the closed Findings contract and verify cache reset clears the advisory

Verification

• npm run fmt:rust:check
• npm run lint:rust
• npm run test:rust:core
• npm run test:rust:daemon
• npm run test:contracts

The API, web, and documentation companions will be stacked separately.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-02T16:56:49.961016Z	134b356	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 134b356769

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Scope reciprocal dependencies to one Compose project

When separate Compose projects expose complementary unique service names—for example, project A's frontend declares backend while project B's backend declares frontend—the collector retains only the service name and ContainerAliases::resolve_dependency resolves it globally. These lines therefore accept the resulting cross-project edges as reciprocal because they share the same snapshot time and revision, emitting a mutual-dependency advisory even though neither project has a cycle. Preserve the Compose project identity and require both declarations to belong to the same project.

Useful? React with 👍 / 👎.