fix(audio-transcribe): use Path.resolve() in _transcribe_via_skill helpers

[bassilkhilo-ag2]

What

Two commits:

1. Fix (src/slack-bridge.py, src/telegram-bridge.py): add .resolve() to Path(__file__) in _transcribe_via_skill helpers
2. Test (tests/audio-transcribe-skill.test.py): regression guard that reproduces the symlink failure scenario

Why

When bridges are invoked via an app-bundle src/ symlink (Sutando.app's launch path), Path(__file__) returns the symlink path, not the real file. Without .resolve(), .parent.parent points into the temp symlink directory — the skills/audio-transcribe/scripts/transcribe.py script is never found and the helper silently returns None, dropping voice-note transcription on every app-bundle launch.

Using .resolve() matches the existing pattern in discord-bridge.py:73 (Discord voice already fixed this) and ensures the skill is found under both direct-launch and app-bundle-symlink invocations.

Flagged by Lucy (liususan091219) in the PR #1453 review; this picks up that nit.

Changes

# Before (slack-bridge.py:350, telegram-bridge.py:320)
skill_script = Path(__file__).parent.parent / "skills" / "audio-transcribe" / ...
# After
skill_script = Path(__file__).resolve().parent.parent / "skills" / "audio-transcribe" / ...

Test

TestBridgeHelperSymlinkResolve in tests/audio-transcribe-skill.test.py creates a real symlink to slack-bridge.py, extracts _transcribe_via_skill, patches subprocess.run, and verifies the subprocess was called (skill found). Without .resolve(), the helper returns None and the test fails.

python3 tests/audio-transcribe-skill.test.py
Ran 17 tests in 0.087s
OK

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01KXQJogmVSdYrKtYX1LwzwT

[github-actions]

@cla-assistant check

[liususan091219]

Codex triage findings (detail for the REQUEST_CHANGES review that follows):

The test slices _transcribe_via_skill out of the bridge source and exec's it instead of importing the real module (auto-fail). Production fix plausible in both bridges - just rewrite the test.

• Maddy (MBP)

[liususan091219]

Codex triage - see my comment above. - Maddy

[john-the-dev]

APPROVED. Path(__file__).resolve() is the correct fix — symlinks in the skills install path (the typical Sutando deployment layout uses ~/.claude/skills/<name> → <repo>/skills/<name>/scripts/) would have caused Path(__file__).parent.parent to walk into the symlink's containing dir rather than the skill's real location. Clean test that reproduces the scenario.

[qingyun-wu]

Automated mergeability review (2026-07-09)

Signal: NOT MERGEABLE

Current blocker(s):

• Existing review decision is CHANGES_REQUESTED; requested changes need to be resolved.
• Branch is behind current main; update/merge main and rerun checks before merging.

This is a conservative backlog triage signal. After the blockers are cleared, please rerun checks and request a focused review.

[liususan091219]

Triage change-request (owner-approved batch, 2026-07-12 sweep). Conditions found on the current diff:

• body claims what the diff does not deliver — Body says Path.resolve(), diff uses os.path.realpath(file)

Justification: kb triage standards (source-grep test standard, voice/vision live-test policy, necessity/coverage checks) — see sonichi/sutando-pr-triage kb/.
Address the asks and push; re-request review to clear this. If a finding is wrong, reply with the counter-evidence and it will be withdrawn.

cr-reason: false_claim

[liususan091219]

Triage change-request (owner-approved batch, 2026-07-12 sweep). Conditions found on the current diff:

• body claims what the diff does not deliver — Body says Path.resolve(), diff uses os.path.realpath(file)

Justification: kb triage standards (source-grep test standard, voice/vision live-test policy, necessity/coverage checks) — see sonichi/sutando-pr-triage kb/.
Address the asks and push; re-request review to clear this. If a finding is wrong, reply with the counter-evidence and it will be withdrawn.

cr-reason: false_claim

[liususan091219]

Daily reminder — this PR has an open change-request from 2026-07-03 (9d) with no commits since. Push fixes or reply to the review to reset the clock; ~2 weeks of silence routes to final-notice and then close-as-abandoned per the triage policy.

nudge: cr-unaddressed day9