Expand editOutcome schema with code fields + add rules to chatInteraction

[sestinj]

Summary by cubic

Added a developer data guide and expanded the editOutcome event schema to include code fields for more detailed logging.

• New Features
  • Added a markdown guide explaining how development data is collected, stored, and configured.
  • Updated the editOutcome schema to log previous and new code, code line counts, and line changes.

[netlify]

✅ Deploy Preview for continuedev ready!

Name	Link
🔨 Latest commit	c7cea2e
🔍 Latest deploy log	https://app.netlify.com/projects/continuedev/deploys/686edba68b53b30008e4a53b
😎 Deploy Preview	https://deploy-preview-6522--continuedev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

⚠️ Conventional Commit Format

Your commit messages don't follow the conventional commit format, but this won't block your PR from being merged. We recommend downloading this extension if you are using VS Code.

Expected Format:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[cubic-dev-ai]

cubic reviewed 2 files and found no issues. Review PR in cubic.dev.