Fix broken links: automation URL and Ask Fern footer links (#4434)

Author: github-actions[bot]

fern/components/FernFooter.tsx

@@ -440,7 +440,7 @@ export default function FernFooter() {
               <div className="fern-cf-column-links">
                 <a href="/learn/sdks/overview/introduction" className="fern-cf-link">SDKs</a>
                 <a href="/learn/docs/getting-started/overview" className="fern-cf-link">Docs</a>
-                <a href="/learn/ask-fern" className="fern-cf-link">Ask Fern</a>
+                <a href="/learn/docs/ai-features/ask-fern/overview" className="fern-cf-link">Ask Fern</a>
                 <a href="/learn/cli-api-reference/cli-reference/overview" className="fern-cf-link">CLI Reference</a>
               </div>
             </div>

fern/products/api-def/pages/project-structure.mdx

@@ -70,7 +70,7 @@ For the other specification formats ([OpenAPI](/api-definitions/openapi/overview
 There are three common ways to manage your API definition:
 
 - **Commit directly into your Fern repository (recommended).** Check your API definition file into the same repository that contains your Fern configuration. This is the simplest approach if you don't maintain the definition elsewhere.
-- **Sync from a source code repository.** Store your API definition in the same repo as your API source code and sync updates into your Fern repository. You can automate this with the [`fern api update`](/cli-api-reference/cli-reference/commands#fern-api-update) CLI command or the [sync-openapi GitHub Action](/api-definitions/openapi/automation).
+- **Sync from a source code repository.** Store your API definition in the same repo as your API source code and sync updates into your Fern repository. You can automate this with the [`fern api update`](/cli-api-reference/cli-reference/commands#fern-api-update) CLI command or the [sync-openapi GitHub Action](/learn/api-definitions/openapi/sync-your-open-api-specification).
 - **Host at a public URL.** Serve the definition from a publicly accessible endpoint and configure the [`origin`](/learn/sdks/reference/generators-yml#openapi) field in `generators.yml` so Fern can fetch it. This is useful when you want a single canonical definition that multiple consumers can reference.
 
 ## Multiple APIs

footer/src/FernFooter.tsx

@@ -298,7 +298,7 @@ export const FernFooter: React.FC = () => {
               <div className="footer-column-links">
                 <a href="/learn/sdks/overview/introduction" className="footer-link">SDKs</a>
                 <a href="/learn/docs/getting-started/overview" className="footer-link">Docs</a>
-                <a href="/learn/ask-fern" className="footer-link">Ask Fern</a>
+                <a href="/learn/docs/ai-features/ask-fern/overview" className="footer-link">Ask Fern</a>
                 <a href="/learn/cli-api-reference/cli-reference/overview" className="footer-link">CLI Reference</a>
               </div>
             </div>