Refactor/extract file replace

Merged
VA
6d ago
+12362-1459

User description

Summary by cubic

Adds the Makerdiary nRF52840 dongle as the primary development board, with FIDO2 passkeys, tap-based pam_u2f login, and Git commit signing; the ESP32-C6 remains a test board. The nRF bootloader accepts only signed firmware and does not expose flash, but the board is not yet suitable for real secrets.

  • Backups include passkeys in sealed sectors; restores support --only for named items.
  • The CLI adds passkey management, commit and GitHub setup, vault-grouped listings, and /settings; it refuses to guess when multiple keys are connected.
  • 1Password sync reuses saved Developer Environments, tap-protects SSH private keys, and skips Documents.
  • Button handling rejects bounce and cancelled requests; CTAPHID requests use separate channels and the authenticator locks when idle.
  • File replacement is atomic for configuration and cache files.

CodeAnt-AI Description

Add nRF52840 support with passkeys, tap-based login, and commit signing

What Changed

  • Adds the Makerdiary nRF52840 dongle as the primary key board while keeping the ESP32-C6 supported. The nRF52840 accepts signed firmware updates.
  • Lets users manage passkeys with a separate FIDO PIN, enable tap-based sudo and lock-screen login, and sign Git commits with a tap.
  • Backups can include passkeys. Full restores require a five-second hold; users can also restore selected entries without replacing the rest of the key.
  • Groups synced entries by 1Password vault in the shell and brings key-management commands together under /settings.
  • A bouncing or cancelled button request no longer counts as approval, and the CLI asks users to choose when multiple keys are connected.

Impact

✅ Passkeys carried across compatible restores
✅ Tap-approved sudo and Git commits
✅ Fewer accidental button approvals

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.