AIP-103: Refactor asset state routes to by-name/by-uri and add AssetUriRef support

[amoghrajesh]

This is a follow up to: #66073 to solve an inconsistency with the existing assets state API as it is today as pointed out in: #66160 (comment)

What changed:

Asset state routes were previously using a single set of endpoints with ?name= as the identifier. This had two problems:

1. Asset.ref(uri="s3://...") inlets produce AssetUriRef objects which only have .uri, not .name — the task runner can crash at context construction time with AttributeError before user code ran

2. The shape was inconsistent with how the existing /assets execution API works (/by-name and /by-uri as separate endpoints)

The routes are now split into /by-name/ and /by-uri/ sub-prefixes mirroring assets APIs.

GET/PUT/DELETE  /state/asset/by-name/value?name=<n>&key=<k>
DELETE          /state/asset/by-name/clear?name=<n>
GET/PUT/DELETE  /state/asset/by-uri/value?uri=<u>&key=<k>
DELETE          /state/asset/by-uri/clear?uri=<u>

Testing

By Name

1. Using this DAG:

from airflow.sdk import DAG, Asset, task

MY_ASSET = Asset("test_events", uri="s3://data-lake/test-events")

with DAG("asset_dag", schedule=None) as dag:

    @task(outlets=[MY_ASSET])
    def produce():
        print("name=test_events  uri=s3://data-lake/test-events")

    produce()

2. Pushed a asset state API

3. Get API by name

4. Delete API by name

By URI

1. Pushed a asset state API with uri

2. Get Asset event by uri

3. Delete API by URI

---

Was generative AI tooling used to co-author this PR?

• Yes : claude sonnet 4.6

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.