Same origin but insertion refused: browser origin, page and storage boundaries

Same origin is not the same page, draft or operation authority

CollieWebSession.isTrusted compares baseURL scheme/host/effective port and invalidation state, not similar-looking titles/domains. Persistent WebKit storage is derived from normalized origin; paths/workbench names do not automatically create separate stores. Insertion can still check expectedPageURL, requestID and adapters. Origin acceptance is not sending permission.

Different from feed URLs, context and restored drafts

Feed review concerns source addresses, context concerns conversation, drafts concern local ownership. Here browser-origin comparison, storage keys and page insertion conditions matter. No page, Cookie or setting is accessed.

Check Verified scope Manual review Not established
Native comparison Lowercased scheme/host and effective port Configured boundary/current URL Trusted account/content certification
Default ports HTTPS 443/HTTP 80 per implementation Implicit/explicit default Downgrade to HTTP for compatibility
Path/title Not this origin identity key Actual page/full-URL conditions Matching appearance grants authority
Persistent key Identifier derived from normalized-origin SHA Same-origin container reuse Every workbench name has isolated cookies
Store versus account Cookie path/login separately Actual account/access Shared container guarantees one identity
Page/request Optional expectedPageURL/prepared request etc. Current page/request ownership Origin bypasses target guards
Adapter outcome Refusal/unknown is not blind fallback Actual result/draft state Insertion means sending/approval
Other native data Radar/notes use separate paths Separate storage surfaces WebKit is the entire archive

Synthetic origin comparison

https://example.com/a and https://example.com:443/b can derive the same origin storage key without being the same page/draft. A handoff bound to the original page still follows that path’s conditions.

isTrusted is not site-safety, account-truth or Agent-memory certification. Shared storage does not establish effective business login. Examples were not fetched and no browsing data was read.

FAQ

Can same origin write into any input?

No. Original page/request/focus/adapter/caller guards remain.

Do different workbench names isolate cookies?

Not by naming; the cited key derives from normalized origin.

Are implicit HTTPS port and explicit 443 necessarily different origins?

This effective-port comparison relates defaults; full-page conditions are separate.

Does one container prove one account?

No. Actual Cookie scope/login/service authority remain.

Is isTrusted security/truth certification?

No. Implementation conditions do not replace content/identity/permission evidence.

Were pages/Cookies checked?

No login, data access or configuration change occurred; fixed source only.

Reading and source

Feed URL differences · Target/context · Native drafts · Workbench scope · Start · Privacy

Origin/storage/insertion · Adapter guards