docs: narrow env-var notes to OAuth scope, defer Fabric mechanics to Harper docs

github-actions[bot] · claude · github-actions[bot] · commit 68dc649005f9 · 2026-04-23T15:25:55.000Z
Remove CI/CD injection guidance (belongs with deploy-CLI credentials, not runtime secrets). Replace with a pointer to Harper Fabric documentation for managing runtime env vars. Preserve local-dev framing and .env warning. Addresses review feedback on PR #55. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
diff --git a/README.md b/README.md
@@ -39,7 +39,7 @@ export OAUTH_GITHUB_CLIENT_ID="your-client-id"
 export OAUTH_GITHUB_CLIENT_SECRET="your-client-secret"
 ```
 
-> **Note:** The `export` commands above are for local development and quick testing only. You can also use a `.env` file with `dotenv-cli` for local dev — just don't commit it. For **Harper Fabric** deployments, inject secrets through your CI/CD pipeline as environment variables (e.g., GitHub repository secrets passed via the `env:` block in your workflow) rather than committing them to any file.
+> **Note:** The `export` commands above are for local development and quick testing only. You can also use a `.env` file with `dotenv-cli` for local dev — just don't commit it. For **Harper Fabric** deployments, see the [Harper Fabric documentation](https://docs.harperdb.io/docs/fabric/managing-applications) for managing runtime environment variables.
 
 ### 3. Configure OAuth Callback
 
diff --git a/docs/getting-started.md b/docs/getting-started.md
@@ -34,7 +34,7 @@ export OAUTH_GITHUB_CLIENT_SECRET="your_github_client_secret"
 
 > **Note:** These `export` commands are for local development only. You can also use a `.env` file with `dotenv-cli` for local dev — just don't commit it to source control.
 >
-> For **Harper Fabric** deployments, inject secrets through your CI/CD pipeline as environment variables (e.g., GitHub repository secrets passed via the `env:` block in your workflow) rather than committing them to any file.
+> For **Harper Fabric** deployments, your app-root `.env` is deployed alongside your component, so the same `.env` you use locally works in production — see the [Harper Fabric documentation](https://docs.harperdb.io/docs/fabric/managing-applications) for managing runtime environment variables.
 
 ### 3. (Optional) Register Lifecycle Hooks
 

Original file line number	Diff line number	Diff line change
`@@ -34,7 +34,7 @@ export OAUTH_GITHUB_CLIENT_SECRET="your_github_client_secret"`
`34`	`34`
`35`	`35`	> Note: These `export` commands are for local development only. You can also use a `.env` file with `dotenv-cli` for local dev — just don't commit it to source control.
`36`	`36`	`>`
`37`		-> For Harper Fabric deployments, inject secrets through your CI/CD pipeline as environment variables (e.g., GitHub repository secrets passed via the `env:` block in your workflow) rather than committing them to any file.
	`37`	+> For Harper Fabric deployments, your app-root `.env` is deployed alongside your component, so the same `.env` you use locally works in production — see the [Harper Fabric documentation](https://docs.harperdb.io/docs/fabric/managing-applications) for managing runtime environment variables.
`38`	`38`
`39`	`39`	`### 3. (Optional) Register Lifecycle Hooks`
`40`	`40`