2026-09-12
Ronova Syuku — Regular · Bold · Italic · BoldItalic
戶你查 · 戶你查 · 戶你查 · 戶你查
Devlog
A public record of what readers can verify.
This log records user-facing changes and current publication boundaries. Operational implementation details stay in a protected record.
Passkey sign-in now begins when Renkan ID opens.
When a protected interface sends you to Renkan ID, the page checks for an available passkey while it loads and can continue with device verification without an extra method-selection click.
- An existing Renkan ID session is recognized before a new sign-in prompt appears.
- Face ID, Touch ID, or the device equivalent can complete an available passkey sign-in.
- Password, explicit passkey, biometric, and email-code fallbacks remain available.
Public release notes narrowed to user-facing changes.
The public devlog now records observable behaviour and publication decisions instead of exposing internal operational detail.
- Public notes describe changes a reader can verify from the public surface.
- Account identifiers, recovery parameters, bridge details, migration references, and internal capability details stay out of this page.
- Renkan ID remains the sole persistent identity authority across connected projects.
The public profile now uses the current role description.
Homepage, About, metadata, and profile text now describe Ronova as a developer and creator working across software, language, systems, and design.
- Outdated role wording has been removed from the public identity surfaces.
- Project ownership and identity boundaries remain explicit.
Renkan is described as a coordination layer.
The Ronova project description now presents Renkan as the shared coordination, identity, and interoperability layer for participating projects.
- Connected projects keep their own governance, data, and authority.
- Future sectors do not define the current public system.