docs: surface Config Composer, editor disables, and top-level function FAQ

Mirror the most impactful README additions into the docs site page so
browser visitors don't have to hop to npm for advanced usage:

- Config Composer section under Usage (fluent .override() / .remove())
- Editor Specific Disables section above FAQ (isInEditor behaviour)
- FAQ section with the top-level function style explanation

README stays the complete reference; the docs page keeps its quick-start
shape but covers the three topics users hit most often.

Author: amondnet

docs/content/1.eslint-config/1.index.md

@@ -76,6 +76,25 @@ export default pleaseai(
 )
 ```
 
+### Config Composer
+
+`pleaseai()` returns a [`FlatConfigComposer`](https://github.com/antfu/eslint-flat-config-utils#composer), so you can fluently override, prepend, or remove named config blocks when the plain options object isn't granular enough:
+
+```ts [eslint.config.ts]
+import pleaseai from '@pleaseai/eslint-config'
+
+export default pleaseai()
+  .override('antfu/stylistic/rules', {
+    rules: {
+      'style/generator-star-spacing': ['error', { after: true, before: false }],
+    },
+  })
+  .renamePlugins({
+    'old-prefix': 'new-prefix',
+  })
+  .remove('antfu/stylistic')
+```
+
 ## NPM Scripts
 
 Add the lint commands to your `package.json` script section:
@@ -101,6 +120,45 @@ Run `npm run lint` to check if the code style is correct, or `npm run lint:fix`
 | `typescript` | `true` |
 | `gitignore` | `true` |
 
+## Editor Specific Disables
+
+When ESLint runs inside a code editor, a handful of rules (`prefer-const`, `unused-imports/no-unused-imports`, `test/no-only-tests`, several `pnpm/*` rules) report as non-fixable so your editor doesn't aggressively rewrite code you're still typing. The same rules apply normally when you run `eslint` in the terminal or through a pre-commit hook, so nothing slips through.
+
+If you want editor and CLI to behave identically, opt out:
+
+```ts [eslint.config.ts]
+import pleaseai from '@pleaseai/eslint-config'
+
+export default pleaseai({
+  isInEditor: false,
+})
+```
+
+## FAQ
+
+### Top-level function style?
+
+PleaseAI re-enables `antfu/top-level-function`, so top-level functions should use a `function` declaration rather than an arrow assigned to a `const`. Arrow functions are still fine inside function bodies, as callbacks, or for inline JSX handlers — the rule only targets top-level declarations.
+
+```ts
+// ✓ preferred
+export function greet(name: string) {
+  return `Hello, ${name}`
+}
+```
+
+Override it if you disagree:
+
+```ts [eslint.config.ts]
+import pleaseai from '@pleaseai/eslint-config'
+
+export default pleaseai({
+  rules: {
+    'antfu/top-level-function': 'off',
+  },
+})
+```
+
 ## VS Code Integration
 
 Install the [ESLint extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) and add to your `.vscode/settings.json`: