[PR] Fix docs referring to a non-existent MetastoreStateBackend class [airflow]

["shahar1 (via GitHub)" <gi...@apache.org>]

shahar1 opened a new pull request, #73080:
URL: https://github.com/apache/airflow/pull/73080

   ## Human Summary
   Fixes outdated references to `MetastoreBackend` in docs and comments.
   
   ## AI Summary
   
   <details><summary>Click here</summary>
   The default state store backend class is `MetastoreBackend` (`airflow.state.metastore.MetastoreBackend`), but several places referred to a `MetastoreStateBackend` that does not exist. Readers following the docs landed on a name they could not find, and the `:class:` cross-reference in the common.io provider docs could not resolve.
   
   Renamed every reference to the real class name:
   
   - `providers/common/io/docs/state_store_backend.rst` — broken `:class:` cross-reference
   - `shared/state/src/airflow_shared/state/__init__.py` — `BaseStoreBackend` docstring
   - two `test_*_state_store.py` class docstrings
   - `AGENTS.md` (also fixes the stale route-handler path in the same sentence: `airflow/core_api/` → `airflow/api_fastapi/core_api/`)
   
   `dev/skill-evals/last-eval-hash.txt` is updated because `AGENTS.md` changed; the eval was re-run and both arms behave identically.
   
   No newsfragment: documentation/comment wording only, no behaviour change.
   </details>
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5)
   
   Generated-by: Claude Code (Opus 5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Fix docs referring to a non-existent MetastoreStateBackend class [airflow]

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk merged PR #73080:
URL: https://github.com/apache/airflow/pull/73080


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Fix docs referring to a non-existent MetastoreStateBackend class [airflow]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on PR #73080:
URL: https://github.com/apache/airflow/pull/73080#issuecomment-5654087933

   ### Backport failed to create: v3-3-test. View the failure log <a href='https://github.com/apache/airflow/actions/runs/34764570106'> Run details </a>
   
   Note: As of [Merging PRs targeted for Airflow 3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in [#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) Slack channel.
   
   <table>
       <tr>
           <th>Status</th>
           <th>Branch</th>
           <th>Result</th>
       </tr>
       <tr>
           <td>❌</td>
           <td>v3-3-test</td>
           <td><a href="https://github.com/apache/airflow/commit/485107f1340a167e7ae68cfed8667c9f7cfb4e0d"><img src='https://img.shields.io/badge/Commit-485107f-red' alt='Commit Link'></a></td>
       </tr>
   </table>
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 485107f v3-3-test
   ```
   
   This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
   the files that need manual conflict resolution.
   
   After you have resolved the conflicts, you can continue the backport process by running:
   
   ```bash
   cherry_picker --continue
   ```
   
   If you don't have cherry-picker installed, see the [installation guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org