chore: unify bold syntax to single asterisk in .org files and update legacy memex-amero references

This commit is contained in:
2026-04-01 12:37:45 -04:00
parent 78ba3112cb
commit d364f90ff6
102 changed files with 955 additions and 955 deletions

View File

@@ -4,7 +4,7 @@
#+FILETAGS: :auth:oauth:google:security:psf:
* Overview
This skill implements the **Headless OAuth 2.0** handshake for Google services. It enables the agent to acquire and rotate `access_tokens` for Gemini without requiring a local browser session, using a "Copy-Paste" authorization code flow.
This skill implements the *Headless OAuth 2.0* handshake for Google services. It enables the agent to acquire and rotate `access_tokens` for Gemini without requiring a local browser session, using a "Copy-Paste" authorization code flow.
* Phase A: Demand (PRD)
:PROPERTIES:
@@ -15,10 +15,10 @@ This skill implements the **Headless OAuth 2.0** handshake for Google services.
Provide a secure, professional OAuth 2.0 interface for Google Gemini.
** 2. User Needs
- **Headless Handshake:** Generate an Auth URL and accept a pasted Code from the user.
- **Token Persistence:** Securely store `refresh_token` in a Lisp state file.
- **Auto-Rotation:** Automatically exchange the `refresh_token` for a new `access_token` when expired.
- **Environment Driven:** Pull `CLIENT_ID` and `CLIENT_SECRET` from system settings.
- *Headless Handshake:* Generate an Auth URL and accept a pasted Code from the user.
- *Token Persistence:* Securely store `refresh_token` in a Lisp state file.
- *Auto-Rotation:* Automatically exchange the `refresh_token` for a new `access_token` when expired.
- *Environment Driven:* Pull `CLIENT_ID` and `CLIENT_SECRET` from system settings.
** 3. Success Criteria
*** TODO Generate valid Google OAuth Authorization URL