/** @file the webkey page at /cache/: a skeleton the key's holder drives over /api. */
/**
* the webkey page, identical for every key (docs/webkeys.md): the key
* rides the URL fragment, which browsers never send to the server or in a
* Referer. Its script reads it, trades it for a capability
* (`api.cache(key)`, Cap'n Web over /api, in-band), and drives the fill
* job. Each round trip is its own HTTP batch session.
*
* Without a fragment it is a login form a password manager fills
* (petname as username, cache id as password). The inputs have no
* `name`, so a native submit (script failed) sends nothing; the key stays
* in memory, out of the address bar and history.
*/
export const CACHE_PAGE_HTML = `
diigo cache
diigo cache
← home
`;