Is this a proposal or a group of proposals? #56

part of why this proposal has been somewhat difficult to follow is that we seem to have two viewpoints:

• the README reads as if it is a very high level community-group-like initiative which could produce many proposals
• the proposal doc reads as if it is a single proposal for a new web API

similarly, i've felt like im not on the same page as many of you in these discussions and i think it is a result of the same thing. i have been seeing this repo as if it is the proposal for a new web API (navigator.provideContext or whatever we call it).

meanwhile, others seem to see it as a much higher level thing, of how browsers as a whole can interact with agents.

if it is the latter, that suggests we could end up writing many proposals over time which collectively make up "web MCP". that makes sense but isn't how this repo is currently positioned or structured - right now we seem to have a big mixture of both. Some issues focus on the web API, some focus on high level questions beyond that.

if it is a group of proposals, maybe we should at least organise the repo to make that clear? a proposals/ directory which has the web API in there clearly defined in isolation. Then update the README To make that very clear.