Fix misleading auth docs and Grok token instruction

api-docs.txt: token is NOT the dossier ID — it's a time-limited encrypted
string. Point users to /connect for token generation.

install_public.tmpl: Grok prompt now points to /connect (Grok tab) for
the token, not /dashboard which doesn't show it.

portal/static/api-docs.txt

@@ -4,9 +4,10 @@ inou Health API
 Base URL: https://inou.com
 
 Authentication: Bearer token in Authorization header, or token query parameter.
-Your token is your dossier ID (16-character hex).
+Get your token from https://inou.com/connect (sign in, then click the Grok tab).
+Tokens are time-limited and encrypted — they are not the same as your dossier ID.
 
-Example: Authorization: Bearer abc123def456789a
+Example: Authorization: Bearer aBcDeFgH1234...(96-character encrypted string)
 
 
 DATA TYPES

portal/templates/install_public.tmpl

@@ -140,7 +140,7 @@ Then fetch https://inou.com/api/v1/dossiers?token=YOUR_ACCOUNT_TOKEN to list my
 Help me explore my health data - imaging studies, genome variants, and lab results.
 
 IMPORTANT:
-- Replace YOUR_ACCOUNT_TOKEN with your token from inou.com/dashboard.
+- Replace YOUR_ACCOUNT_TOKEN with your token from inou.com/connect (sign in, go to the Grok tab).
 - Allow 3 seconds for API responses before assuming failure.
 - When sharing image links, use the exact image_url from responses.
 - This is real medical data. NEVER hallucinate. Only describe what you actually see.</pre>