fix(logs): avoid loading local project resources

[davidsu]

Note

Description

base44 logs used to read the local project config to figure out which functions to fetch logs for. That meant an unrelated local config error (e.g. an invalid entity file) could break a purely remote, read-only command, and the "function not found" hint listed local functions rather than what is actually deployed. This PR makes the command source function names exclusively from the deployed-functions API, and only when it actually needs them.

It also hardens the 404 path: the available-functions hint is now looked up lazily, and if that lookup fails the original logs error is rethrown instead of being masked by a secondary failure. When the hint does succeed, the 404 is attached as the cause of the resulting InvalidInputError.

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

• Dropped readProjectConfig / getProjectFunctionNames from logs.ts — the command no longer loads local project resources, so a broken local config cannot fail a remote log fetch.
• Function names are now resolved only from listDeployedFunctions(), and only when --function is omitted; with --function specified no list call is made at all.
• Added getFunctionNamesForHint(): on a 404 it lazily fetches deployed function names for the hint, and rethrows the original logs error if that fetch fails, so a secondary error never masks the real one.
• The InvalidInputError for a missing function now carries the 404 ApiError as its cause, and the hint text reads "Available functions in this app" instead of "in this project".
• Unified the empty-state message to "No functions found in this app." (no more local/remote split).
• Updated the --function help text to say logs are fetched for "all deployed functions" when the flag is omitted.
• Tests: added coverage for skipping local resources with --function, listing deployed names in the 404 hint, and preserving the original error when the hint lookup fails; reworked existing tests to mock the functions list and removed now-unnecessary mocks.

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (npm test)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated docs/ (AGENTS.md) if I made architectural changes

Additional Notes

Behavior change worth noting: inside a local project, base44 logs with no --function now lists logs for functions deployed to the app rather than functions declared locally. Functions that exist locally but have never been deployed will no longer appear — which matches what the logs API can actually return.

The test suite was not executed in this environment (running it needs bun run build first), so the "tested locally"/"all tests pass" boxes are left unchecked pending CI.

---

_{🤖 Generated by Claude | 2026-08-27 10:26 UTC | 4743740}

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.1.10-pr.607.4743740

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.1.10-pr.607.4743740"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.1.10-pr.607.4743740"
  }
}

• 📦 Preview Package: @base44-preview/cli@0.1.10-pr.607.4743740
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}

[talge-a11y]

see my note