refactor: resolve 4 file-level dependency 2-cycles (architecture backlog) #32
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
h-dv/code-index#32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From the 2026-07-20 brainstorm architecture lens (
_prdoc/records/brainstorm-2026-07-20-index-data-catalog.md) — real cycles in the current codebase, verified oversymbol_edges. Not bugs (declined for the v0.5.19 fix round), but each is a pair of files that cannot be edited independently:crates/cli/src/main.rs ↔ crates/cli/src/link.rscrates/cli/src/main.rs ↔ crates/cli/src/doctor.rscrates/indexer/src/db.rs ↔ crates/indexer/src/migrations.rscrates/daemon/src/access.rs ↔ crates/daemon/src/local_index.rs(A fifth, in the ruby test fixtures
user.rb ↔ post.rb, is intentional fixture content.)Suggested direction: extract the shared surface each pair trades (e.g. cli main's arg structs vs subcommand entry points; db.rs's open/pragma helpers vs migrations' run) so the edges point one way. Once #28 (detect_cycles) ships, its conformance mode can enforce cycle-freedom in CI.
Triage: P3 internal architecture backlog
Keep this as tech debt, separate from the agent-product roadmap. Do not refactor solely to satisfy a cycle metric: verify each direction represents harmful ownership coupling and that extraction produces a simpler one-way boundary.
After #28 exists, use it to record the baseline and prove each change removes a production SCC without creating another. The intentional Ruby fixture cycle should remain explicitly excluded/labeled.