I have an existing Chrome extension built to automate a set of browser tasks. I own the full, unobfuscated source code, but the same workflow now needs to live inside a different, slimmer extension. To move the logic across, you will first study and fully map how the current code handles task automation, then recreate that behaviour in the new project. Because the original author heavily relies on custom obfuscation, a solid grasp of both obfuscation and de-obfuscation techniques is essential; the final build should be equally well-protected and performance-friendly. Beyond matching every automated step, I also expect clean, well-commented source files (before obfuscation), concise build instructions, and a short read-me summarising how the logic was ported. Acceptance criteria • All automated workflows behave identically to the original extension. • Final bundle is obfuscated to a comparable level. • No console errors or Chrome Web Store policy violations. • Hand-off includes unobfuscated source, obfuscated build, and documentation.