From 443fd1d325f90712b091960987f31501c75bd5b3 Mon Sep 17 00:00:00 2001 From: Sri Pasumarthi Date: Wed, 13 May 2026 17:19:58 -0700 Subject: [PATCH] fix(docs): add strict configuration traversal and partner integration rules to project memory Updates GEMINI.md with explicit development conventions for end-to-end state lifecycle tracing, centralized architectural mapping, and treating existing client integration profiles as immutable contracts. --- GEMINI.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/GEMINI.md b/GEMINI.md index 4acdfc08be..161711d0a3 100644 --- a/GEMINI.md +++ b/GEMINI.md @@ -78,6 +78,18 @@ powerful tool for developers. - **License Headers:** For all new source code files (`.ts`, `.tsx`, `.js`), include the Apache-2.0 license header with the current year. (e.g., `Copyright 2026 Google LLC`). This is enforced by ESLint. +- **Configuration Lifecycle Tracing:** When modifying state, credentials, or + network options, thoroughly trace the data traversal pipeline from initial + environmental capture down to the target consumer option layer to ensure + downstream conditional mapping does not undermine intended states. +- **Architectural Consistency:** Centralize shared configuration logic (such as + auth inference) inside common configuration modules rather than isolating + inference to specific entry points, ensuring absolute uniformity across + interactive CLI usage, background jobs, and programmatic SDK embeddings. +- **Partner & Client Invariants:** Treat established integration profiles and + edge-case workarounds as immutable contracts. Ensure new validation routes + specifically fall back to or preserve legacy mapping to prevent behavioral + regressions for active sidecars. ## Testing Conventions