fix 403 error

[SharonStrats]

I just confirmed this is no longer needed to fix the PATCH issue, but it does remove the 403 errors.

Want to speak to Timea first about this.

[Copilot]

🟡 Changes recommended

The new fallback introduces inconsistent use of DEFAULT_PROFILE_PATH, misleading indentation, and an inaccurate error message that can hinder debugging.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR adjusts WebID/profile resolution logic to avoid relying on a “default profile at pod root” assumption (likely related to the reported 403), and introduces a new fallback that tries loading the root-origin profile card.

Changes:

• Removes the initial “pod root + DEFAULT_PROFILE_PATH” load attempt from both loadProfileFromURI and getNameOfPodOwner.
• Adds a new fallback that tries ${origin}/profile/card#me when there is no first path segment to derive a prefixed pod from.

File summaries

File	Description
src/utils/webIdUtils.ts	Updates WebID/profile discovery fallbacks to prefer derived or origin-root profile card loading.

Review details

Suppressed comments (1)

src/utils/webIdUtils.ts:85

• This catch covers failures from both the derived-profile attempt and the new rootWebId fallback, but the log message still says "failed on derived profile". Updating the message avoids misleading diagnostics when the root-profile load is what fails.

      return getName(store, rootWebId)
  } catch (err) {
    if (!isFetchErrorStatus(err, 403)) {
      console.error('getNameOfPodOwner failed on derived profile:', err)
    }

• Files reviewed: 1/2 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.