listen

previous push 1.0.0 failed because it was already published (and
retracted) on pub before moving into core-package. The pub API seems to
still include it as an available version. Thus bump to 1.0.1

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined
  there for submitting PRs.
• I read the AI contribution guidelines and understand my
  responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my
  responsibilities.
• I read and followed the Flutter style guide and ran the
  auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded
  by square brackets, e.g. [vector_math]
• I linked to at least one issue that this PR fixes in the
  description above.
• I followed the version and CHANGELOG instructions, using
  semantic versioning and the repository CHANGELOG style, or I have
  commented below to indicate which documented exception this PR falls
  under¹.
• I updated/added any relevant documentation (doc comments with
  ///).
• I added new tests to check the change I am making, or I have
  commented below to indicate which test exemption this PR falls
  under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code
Assist for
GitHub.
Comments from the gemini-code-assist bot should not be taken as
authoritative feedback from the Flutter team. If you find its comments
useful you can update your code accordingly, but if you are unsure or
disagree with the feedback, please feel free to wait for a Flutter team
member's review for guidance on which automated comments should be
addressed.

1. Regular contributors who have demonstrated familiarity with the
   repository guidelines only need to comment if the PR is not
   auto-exempted by repo tooling. ↩ ↩²

• Pushes stable version.

as title

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined
  there for submitting PRs.
• I read the AI contribution guidelines and understand my
  responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my
  responsibilities.
• I read and followed the Flutter style guide and ran the
  auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded
  by square brackets, e.g. [vector_math]
• I linked to at least one issue that this PR fixes in the
  description above.
• I followed the version and CHANGELOG instructions, using
  semantic versioning and the repository CHANGELOG style, or I have
  commented below to indicate which documented exception this PR falls
  under¹.
• I updated/added any relevant documentation (doc comments with
  ///).
• I added new tests to check the change I am making, or I have
  commented below to indicate which test exemption this PR falls
  under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code
Assist for
GitHub.
Comments from the gemini-code-assist bot should not be taken as
authoritative feedback from the Flutter team. If you find its comments
useful you can update your code accordingly, but if you are unsure or
disagree with the feedback, please feel free to wait for a Flutter team
member's review for guidance on which automated comments should be
addressed.

1. Regular contributors who have demonstrated familiarity with the
   repository guidelines only need to comment if the PR is not
   auto-exempted by repo tooling. ↩ ↩²

• ErrorContext is now a required positional, non-nullable parameter.

flutter/flutter treats different error differently.

For stateError when using changenotifier, it throws synchronously

for Error raise during listener callback, it uses reportError and
continue execution.

Improve the Error API so that framework can tell where the error is
raised

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined
  there for submitting PRs.
• I read the AI contribution guidelines and understand my
  responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my
  responsibilities.
• I read and followed the Flutter style guide and ran the
  auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded
  by square brackets, e.g. [vector_math]
• I linked to at least one issue that this PR fixes in the
  description above.
• I followed the version and CHANGELOG instructions, using
  semantic versioning and the repository CHANGELOG style, or I have
  commented below to indicate which documented exception this PR falls
  under¹.
• I updated/added any relevant documentation (doc comments with
  ///).
• I added new tests to check the change I am making, or I have
  commented below to indicate which test exemption this PR falls
  under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code
Assist for
GitHub.
Comments from the gemini-code-assist bot should not be taken as
authoritative feedback from the Flutter team. If you find its comments
useful you can update your code accordingly, but if you are unsure or
disagree with the feedback, please feel free to wait for a Flutter team
member's review for guidance on which automated comments should be
addressed.

1. Regular contributors who have demonstrated familiarity with the
   repository guidelines only need to comment if the PR is not
   auto-exempted by repo tooling. ↩ ↩²

• Updates ErrorCallback to pass the raw error object and original StackTrace.
• Adds an optional ErrorContext parameter to ErrorCallback to distinguish listener errors from assertion errors.

as title

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined
  there for submitting PRs.
• I read the AI contribution guidelines and understand my
  responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my
  responsibilities.
• I read and followed the Flutter style guide and ran the
  auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded
  by square brackets, e.g. [vector_math]
• I linked to at least one issue that this PR fixes in the
  description above.
• I followed the version and CHANGELOG instructions, using
  semantic versioning and the repository CHANGELOG style, or I have
  commented below to indicate which documented exception this PR falls
  under¹.
• I updated/added any relevant documentation (doc comments with
  ///).
• I added new tests to check the change I am making, or I have
  commented below to indicate which test exemption this PR falls
  under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code
Assist for
GitHub.
Comments from the gemini-code-assist bot should not be taken as
authoritative feedback from the Flutter team. If you find its comments
useful you can update your code accordingly, but if you are unsure or
disagree with the feedback, please feel free to wait for a Flutter team
member's review for guidance on which automated comments should be
addressed.

1. Regular contributors who have demonstrated familiarity with the
   repository guidelines only need to comment if the PR is not
   auto-exempted by repo tooling. ↩ ↩²

• Fixes dart doc example directive.

• Adjusts source code to be publishable.
• Moves source code from flutter/flutter to flutter/core-packages.