fix: decode URI-encoded path segments for files with spaces

Next.js catch-all [...path] segments preserve %20 encoding from the URL.
File paths in the DB use literal spaces, causing folder scope checks and
GitHub API calls to fail on paths like "roadmap docs/README.md".

Added decodeURIComponent to both the share viewer and repo viewer.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: wiseyoda

src/app/repos/[owner]/[repo]/[...path]/page.tsx

@@ -50,7 +50,7 @@ export default async function MarkdownViewPage({
   if (!session) redirect("/");
 
   const { owner, repo, path: pathSegments } = await params;
-  const filePath = pathSegments.join("/");
+  const filePath = pathSegments.map(decodeURIComponent).join("/");
   const branch = await getDefaultBranch(session.accessToken, owner, repo);
 
   const fullRepo = `${owner}/${repo}`;

src/app/s/[id]/[...path]/page.tsx

@@ -63,7 +63,7 @@ export default async function SharedFilePage({
   }
 
   const [owner, repo] = share.repo.split("/");
-  const filePath = pathSegments.join("/");
+  const filePath = pathSegments.map(decodeURIComponent).join("/");
 
   // For folder shares, verify the path is within the shared folder
   if (share.type === "folder" && share.file_path) {