fix(graph): normalize wing slug at init so topic tunnels fire for hyphenated dirs (#1194)

[bensig]

Fixes #1194.

Problem

mempalace init recorded the topics_by_wing registry key under the raw directory name (e.g. mempalace-public), while mempalace.yaml's wing field used the lower-cased + separator-collapsed slug (mempalace_public). At mine time the miner read the slug from the yaml and queried the registry under the wrong key, so _compute_topic_tunnels_for_wing returned 0 silently. Every project whose dirname contained a - or space lost every topic tunnel — the common shape in the wild.

Confirmed in a 5-project end-to-end repro (see #1194 for the table): expected 7 tunnels, got 2 (only the no-separator pair). Direct repro of the lookup miss:

```python

from mempalace.miner import get_topics_by_wing
from mempalace.palace_graph import topic_tunnels_for_wing
m = get_topics_by_wing()
len(topic_tunnels_for_wing('mempal_private', m, min_count=1)) # what mine actually calls
0
len(topic_tunnels_for_wing('mempal-private', m, min_count=1)) # what's in topics_by_wing
5
```

Fix

Extracted the normalization rule into config.normalize_wing_name() and routed both call sites through it:

• mempalace/cli.py:146 — registry write at init time
• mempalace/room_detector_local.py:307 — mempalace.yaml write

The two paths now produce the same key by construction.

Tests

• tests/test_config.py — 4 unit tests for normalize_wing_name (hyphen, space, already-clean, mixed).
• tests/test_cli.py::test_cmd_init_normalizes_wing_name_for_topics_registry — regression test asserting add_to_known_entities is called with the normalized slug when the dirname is hyphenated. This test fails on develop without the fix.
• Full suite: 1310 passed (+5 new).
• ruff check + ruff format --check clean for the changed files.

Why the original tests missed it

tests/test_palace_graph_tunnels.py and tests/test_miner.py topic-tunnel fixtures use wing_alpha, wing_beta, foo, bar — names that look identical before and after normalization. Hyphenated names were never exercised at the init→mine seam.

cc @igorls

[Qodo-Free-For-OSS]

Hi, miner.load_config() falls back to the raw directory basename when mempalace.yaml is missing, but cmd_init now records topics_by_wing under a normalized wing slug, so _compute_topic_tunnels_for_wing() will return 0 due to a key miss in fallback-config scenarios.

Severity: action required | Category: correctness

How to fix: Normalize fallback wing in load_config

Agent prompt to fix - you can give this to your LLM of choice:

Issue description

cmd_init now writes topics_by_wing using normalize_wing_name(dir_basename), but when mempalace.yaml is missing the miner’s load_config() fallback still uses the raw resolved_project_dir.name. This causes _compute_topic_tunnels_for_wing() to miss the registry key and silently skip topic tunnel creation.

Issue Context

• cmd_init() uses normalized wing for registry writes.
• room_detector_local writes normalized wing into mempalace.yaml.
• But mining without a config file uses a raw wing fallback.

Fix Focus Areas

• mempalace/miner.py[277-306]
• (optional) add a regression test covering mining without mempalace.yaml when dirname contains hyphen/space

We noticed a couple of other issues in this PR as well - happy to share if helpful.

---

Found by Qodo code review. FYI, Qodo is free for open-source.

[bensig]

Self-verification (since GH won't let me approve my own PR):

`pytest tests/test_cli.py tests/test_config.py` — 85 passed on this branch.

What I checked

• Single source of truth. `normalize_wing_name()` is now defined once in `config.py` and called from both `cli.py` (`cmd_init` writing `topics_by_wing`) and `room_detector_local.py` (writing `mempalace.yaml`'s `wing` field). Refactored the previously-inline normalization in `room_detector_local.py` to use the shared helper. The `miner` already reads the wing slug from `mempalace.yaml`, so all three writers now agree.
• Regression test. `test_cmd_init_normalizes_wing_name_for_topics_registry` exercises a literal `my-cool-app` dir and asserts `my_cool_app` lands in `topics_by_wing` keys. Fails on the pre-fix code, passes on this branch.
• CHANGELOG entry with the failure mode named explicitly so anyone investigating after the fact sees why hyphenated dirs were silently losing tunnels.

Coordination with #1197

wahajahmed010 has a complementary PR at the lookup layer in `palace_graph.py`. Both should land — this one prevents bad keys from being written, theirs recovers existing palaces with bad keys already on disk. Posted a coordination ask on #1197 suggesting they swap their local `_normalize_wing` for `from .config import normalize_wing_name` after this lands, so we end up with a single source of truth.

Whoever-isn't-me reviews this

Ready for second eyes. Igor or anyone with write access — small surface, covered by tests, low risk.

[igorls]

One small ask before merge: mempalace/convo_miner.py:397 still does the same .lower().replace(" ", "_").replace("-", "_") inline. Now that normalize_wing_name() exists, folding it in keeps all wing-slug producers on one rule and prevents future skew:

from .config import normalize_wing_name
...
wing = normalize_wing_name(convo_path.name)

No behavior change — same output for every input — but the next time the rule shifts, there's only one place to edit.

[igorls]

Pushed c3ee090 covering the two outstanding asks on this PR:

1. miner.load_config no-yaml fallback — was returning the raw dirname as the wing while cmd_init writes topics_by_wing under the normalized slug. Same key-miss class as Topic tunnels silently skipped for wings with hyphenated dir names #1194, just down the no-yaml branch. Now routed through normalize_wing_name. Flagged by Qodo on the original review.
2. convo_miner.py:397 — folded the inline .lower().replace(" ", "_").replace("-", "_") through normalize_wing_name. Pure consolidation, no behavior change for any input. All four wing-slug producers (cmd_init, room_detector_local, miner.load_config fallback, convo_miner) now share one rule.

Added test_load_config_no_yaml_normalizes_hyphenated_wing to lock the fallback path. Full suite green: 1311 passed; ruff check + format clean.

Background fork on a worktree off MemPalace/mempalace's branch — the PR is ready to merge once you give it the second-eye.