mirror of
https://github.com/penpot/penpot.git
synced 2026-10-11 05:37:50 -04:00
Andrey Antukhandalonso.torres
ea3d18c0a5
* ✨ Gate error reporters behind :error-reporting flag Error reporters used to start on every boot with no way to switch them off. They now only start when the new :error-reporting flag is on (off by default, enable with PENPOT_FLAGS=enable-error-reporting). The database reporter needs the flag alone; mattermost needs the flag plus its webhook url. Shutdown with the flag off is safe, and the database loop now honors its runtime switch. AI-assisted-by: muse-spark-1.3-contributor * 📚 Add audit-log reference memory and update dev tooling Adds the top-level audit-log reference memory with all event flows and turns backend/audit-log into a redirect stub. Also includes the staged dev-tooling updates (playwright deps, mdts args, gitignore). AI-assisted-by: muse-spark-1.3-contributor * ✨ Assign server-side initiator to frontend audit events Frontend audit events now carry a server-assigned initiator derived from the x-client header (penpot-frontend goes to app, penpot-admin-console goes to admin-console, legacy penpot-nitrate stays on admin-console, all else goes to app). Client-sent values are always overwritten, and the key survives on telemetry shadow rows. AI-assisted-by: muse-spark-1.3-contributor * 🐛 Keep initiator on frontend telemetry context The strips-pii-keys test still asserted the old contract (initiator stripped). The initiator only names the sending app, so it is not personal data and must survive the telemetry filter like on the backend channel. AI-assisted-by: muse-spark-1.3-contributor * 📚 Document initiator on PostHog and browser origins Complete the audit-log memory for the latest changes: the initiator property forwarded to PostHog on both channels and the eventOrigin rule for admin-console browser events. AI-assisted-by: muse-spark-1.3-contributor * 🐛 Fix unscaped argument in script --------- Co-authored-by: alonso.torres <alonso.torres@kaleidos.net>