Repository navigation
front: restore landing access before resuming the shared session - #36
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[agent:contract]
Ce qui change
La session partagée du keeper ouvrait directement le dashboard et masquait la landing. Chaque chargement ouvre désormais la landing après connexion, même si une session existe. Resume session ouvre le dashboard ; Home revient à la landing. Les deux actions ne changent que l'état React et n'envoient aucun POST. La création explicite d'une session garde son fonctionnement existant.
Autorisation ponctuelle
Liel a explicitement demandé dans ce chat une livraison urgente via PR staging puis PR main et déploiement Vercel, et autorisé son exécution par cet agent. Cette dérogation couvre le périmètre front et les fusions/déploiement de cette correction uniquement. La politique générale d'AGENTS.md n'est pas modifiée. Aucun push direct sur staging/main, aucune transaction Stellar, aucune suppression de session.
Revue
Session Codex neuve indépendante selon A9 : PASS, sans point bloquant. Revue statique de la navigation readonly, restauration/SSE et création explicite. Aucune refonte de DA, aucun changement de keeper/contrat/marge.
Tests
Interfaces
Aucune modification. Session et vault existants préservés ; navigation locale au navigateur.
Documentation
README : comportement landing, Home et Resume session. Règles/spec/plan consultés, pas de changement de gouvernance.
Checklist