Log full error object in interactions endpoint catch block

[Copilot]

Error handling in the interactions endpoint was logging only err.message, losing critical debugging information like stack traces and error properties in production.

Changes

• Updated error logging in /routes/interactions.js to log the full error object

Before:

} catch (err) {
    console.error('Interaction check failed:', err.message);
    res.status(502).json({ error: 'Interaction check failed' });
}

After:

} catch (err) {
    console.error('Interaction check failed:', err);
    res.status(502).json({ error: 'Interaction check failed' });
}

This provides complete error context (stack trace, properties, nested errors) for production debugging.

Original prompt

---

This section details on the original issue you should resolve

<issue_title></issue_title>
<issue_description>

The error handling in the catch block is incomplete. While returning a 500 status is correct, the actual error object (err) is not being logged. This makes debugging failures in production extremely difficult. You should always log the error details.

} catch (err) {
    console.error('Interaction check failed:', err);
    res.status(500).json({ error: 'Interaction check failed'});
}

Originally posted by @gemini-code-assist[bot] in #11 (comment)
</issue_description>

Comments on the Issue (you are @copilot in this section)

@ELMOURABEA UP

• Fixes  #24

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.