Separate middleware context from stream instance

[jamilahmadzai]

Fixes #12.

This separates the middleware-facing context from the public Majo stream instance while keeping the existing fluent stream API intact. Middleware now receives a smaller MajoContext with file helpers, files, meta, and baseDir; source/dest/process/use stay on the outer stream.

What changed:

• added MajoContext and made middleware run against that context instead of the stream instance
• preserved queued pre-process helpers such as filter, transform, rename, createFile, deleteFile, and writeContents
• copied middleware meta and processed files back to the stream after process()
• avoided dependency or lockfile changes

Coverage added:

• middleware context is not the Majo stream and does not expose source/dest/process
• queued file operations keep order across sync and async transforms
• ctx.filter() still works inside middleware
• reassigned ctx.meta is preserved on the stream
• rename works before dest() and helpers still work after process() without reprocessing

Validation:

• corepack yarn install --frozen-lockfile
• corepack yarn test --runInBand (11 passed)
• corepack yarn build
• git diff --check

IssueHunt payout note:

• GitHub: @jamilahmadzai
• PayPal withdrawal email: jamilurrehman722@gmail.com

---

IssueHunt Summary

Referenced issues

This pull request has been submitted to:

• #12: Separate the majo instance and middleware context

---

[vercel]

@jamilahmadzai is attempting to deploy a commit to the EGOIST's projects Team on Vercel.

A member of the Team first needs to authorize it.