Developer install (install-dev.sh / requirements-dev.txt) fails on main: wayflowcore 26.3.0 pins pyagentspec<26.4

Description

The developer installation documented in installation.rst / contributing (bash install-dev.sh, which installs pyagentspec/requirements-dev.txt) cannot resolve on main right now: requirements-dev.txt installs -e .[...,wayflow_oci,wayflow_datastore,wayflow_a2a,...], the wayflow* extras require wayflowcore>=26.3.0, and the released wayflowcore==26.3.0 pins pyagentspec>=26.3.0,<26.4.0, while VERSION on main is 26.4.0.dev0.

The public GitHub CI does not notice because it installs requirements-dev-github.txt (core package only).

Reproduction

git clone https://github.com/oracle/agent-spec && cd agent-spec/pyagentspec
python3.12 -m venv .venv && . .venv/bin/activate
pip install -e '.[wayflow]'

ERROR: Cannot install pyagentspec, pyagentspec 26.4.0.dev0 (from editable .../agent-spec/pyagentspec) and pyagentspec[wayflow]==26.4.0.dev0 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: ...

uv pip install -e '.[wayflow]' reports the same conflict (wayflowcore==26.3.0 depends on pyagentspec>=26.3.0,<26.4.0), and bash install-dev.sh fails at the requirements-dev.txt step.

Expected behavior

A fresh clone of main can be set up for development with the documented commands, or the documentation states how to install the WayFlow extras between releases (for example with BUILD_VERSION=<last release> when building, or by installing wayflowcore with --no-deps).

Suggestion

Either drop the wayflow* extras from requirements-dev.txt (keeping them in an opt-in file), or document the workaround in the installation guide. The pin itself lives in wayflowcore, so it cannot be fixed in this repository alone.

Environment

• main at 26.4.0.dev0, wayflowcore 26.3.0 on PyPI, pip 25.x and uv 0.11, Python 3.12

Start with install-dev.sh, requirements-dev.txt, installation.rst, and the contributing documentation, then reproduce the dependency resolution failure using the documented commands. Check the relationship with requirements-dev-github.txt and verify that a fresh checkout can install successfully, or that the documented release workaround works between releases.