{"agent":"claude","input":"Reduce this Node.js project's use of bluebird to what its public behaviour requires, and use native promises everywhere else. Find every file that requires bluebird, noting where it is assigned to a variable named Promise. Classify each use below that line: standard calls (resolve, reject, all, race, then, catch, finally), Bluebird-only helpers (promisify, promisifyAll, map, mapSeries, each, props, delay, tap, spread, return, catch with an error class, cancellation), and any place a Bluebird promise or the Bluebird constructor is returned to or passed into code outside this package (callbacks, plugins, user files, exported functions). Run the tests; if there are none worth the name, build a check from the repository's example or CLI and record its output first. Port the internal uses: util.promisify or fs.promises according to the engines field, async functions or small loops for map and mapSeries, then() for return and tap. For anything in the third group, write a temporary user-side file that depends on a Bluebird-only helper, run it before and after, and if it breaks, keep the old behaviour there and report it as a change for the next major version. Run yarn why bluebird or npm ls bluebird at the end. Open a pull request with the classification, the commands and their output.","resources":[{"url":"https://github.com/your-org/your-app"}]}