bridge: hard-rename slack-bridge paths/artifacts with migration shims (phase 3)

[benvinegar]

Summary

This is phase 3 of the Gateway bridge rename rollout.

It performs the hard path/artifact rename from slack-bridge to gateway-bridge while keeping migration shims for rollback-safe compatibility.

What changed

1) Hard path rename

• Renamed source directory:
  • slack-bridge/ → gateway-bridge/
• Renamed bridge package metadata:
  • package name is now gateway-bridge
• Updated repo/config tooling to point at gateway-bridge/*:
  • lint/coverage config
  • setup/install/test scripts
  • CI bootstrap/smoke scripts
  • security/doctor/deploy/update flows
  • integration/unit tests

2) Compatibility shims (legacy still works)

• Added source-level compatibility symlink:
  • slack-bridge -> gateway-bridge
• Kept runtime fallback handling for legacy paths/artifacts where relevant:
  • release bridge dir fallback (/opt/baudbot/current/slack-bridge)
  • manifest key fallback (release/slack-bridge/*)
  • supervisor status fallback (slack-bridge-supervisor.json)
  • bridge log fallback (slack-bridge.log)
• Startup migration behavior:
  • bridge now uses gateway-bridge.log
  • legacy slack-bridge.log is migrated/symlinked for continuity
• Tool guard + pre-commit protections cover both new and legacy security file paths.

3) Docs/skills terminology and operator guidance

• Updated AGENTS/skills/runtime notes to use gateway-bridge as primary path/name.
• Retained explicit legacy fallback references for operators during migration window.

Validation

• npm run lint (passes; existing non-blocking unused err warning in broker-bridge remains)
• npm test
• npm run typecheck
• bash bin/test.sh js
• bash bin/test.sh shell

All pass in this branch.

Migration / rollback notes

• Forward migration: new releases run from gateway-bridge paths by default.
• Backward compatibility: legacy slack-bridge path and key fallbacks remain in place for at least this release cycle.
• Rollback safety: status/log/path fallbacks allow older/newer artifacts to coexist during rollback/roll-forward.

[greptile-apps]

Greptile Summary

This PR completes phase 3 of the Gateway bridge rename, performing a hard directory rename from slack-bridge/ to gateway-bridge/ with comprehensive backward compatibility shims.

Key changes:

• Renamed source directory and created symlink slack-bridge -> gateway-bridge for source-level compatibility
• Updated package name to gateway-bridge in package.json
• Updated all references across scripts, configs, tests, and documentation to use new paths
• Implemented runtime fallbacks for legacy paths, logs, manifest keys, and supervisor status files
• Added log file migration logic in startup script that moves slack-bridge.log to gateway-bridge.log and creates compatibility symlink
• Extended security protections (pre-commit hook, tool-guard) to cover both new and legacy paths
• Updated all test files and CI scripts to reference new directory structure

Migration safety:

• All runtime scripts check new path first, then fall back to legacy path if present
• Security audit handles both old and new manifest keys for critical files
• Rollback-safe design allows older and newer releases to coexist during deployment transitions

Confidence Score: 5/5

• This PR is safe to merge with very low risk
• This is a well-executed rename with comprehensive backward compatibility. All references have been systematically updated, security protections remain intact for both old and new paths, and extensive fallback logic ensures safe rollback capability. Tests validate the changes, and the phased approach (this is phase 3) demonstrates careful planning.
• No files require special attention

Important Files Changed

Filename	Overview
slack-bridge	Symlink created for backward compatibility: slack-bridge -> gateway-bridge
gateway-bridge/package.json	Package name updated from slack-bridge to gateway-bridge
pi/skills/control-agent/startup-pi.sh	Bridge startup updated with migration logic for log files and directory fallbacks
bin/security-audit.sh	Security audit updated with fallback logic for legacy manifest keys and directories
hooks/pre-commit	Pre-commit hook protects both gateway-bridge and legacy slack-bridge security files
pi/extensions/tool-guard.ts	Tool guard patterns updated to protect both new and legacy bridge security file paths
bin/deploy.sh	Deploy script updated to use new path and clean up both legacy runtime directories
bin/doctor.sh	Doctor script checks new path first, with legacy path fallback

_{Last reviewed commit: 79a6a53}