fix: remove root tsconfig fallback and add error handling for package tsconfig resolution

[Zih0]

Problem

When running docflow from the root of a monorepo, if a specific package doesn't have its own tsconfig.json, documentation from other packages would incorrectly be generated under that package's output directory.

Root Cause

The tsconfig resolution logic was falling back to the root tsconfig.json when a package-level tsconfig was not found.

Since root tsconfig.json in monorepos typically includes all packages in its include field, this caused the documentation generator to process source files from all packages instead of just the target package.

Solution

• Remove the fallback to root tsconfig.json - each package must have its own tsconfig
• Add try-catch blocks to handle tsconfig resolution error, allowing other packages to continue processing even if one fails

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docflow-docs	Ready	Preview, Comment	Jan 19, 2026 1:51pm

[raon0211]

👍