Configure Lucida for managed Beads

[aelefebv]

Summary

• adopt Lucida's existing Beads project for a Gas City-managed Dolt server
• add the canonical project identity and Gas City ignore/config metadata
• preserve the portable HTTPS sync remote in tracked configuration
• keep Ortega's repo-scoped SSH deploy-key override in ignored config.local.yaml

Why

This prepares Lucida to run as the lucida rig in the persistent Ortega sandbox while preserving repository portability and isolating GitHub write access to Lucida.

The existing Beads history was adopted rather than reinitialized. Its remote Dolt schema was migrated from v49 to v53 by the designated Ortega migrator and published to refs/dolt/data; all 111 issues remain available.

Impact

• no application source changes
• no credentials, VM paths, or SSH aliases added to tracked files
• Lucida remains suspended in Ortega; this PR does not start any agents

Validation

• git diff --check
• independent maintainer, security, and Gas City/Beads operator review
• Gas City configuration validation
• rig initialization, prefix, identity, and cross-rig route checks
• Beads status: 111 total issues (53 open, 58 closed)
• repo-scoped deploy-key authentication and Dolt push verified