devtools Authorize Client bootstrap

[burdettadam]

The current Authorize Client key installs b506607x15.prod on authorization and not the intended b507199x13.prod. Our bootstrap code is hard coded to call b507199x13.prod to check what rulesets are installed. this call fails because b507199x13 is not installed. after manually installing b507199x13, it continues to fail with behavior of not having proper credentials to list installed rulesets or to install needed rulesets.
devtools and wrangler are coded to use b507199x14 as devtools. b506607x15.prod(old bootstrap) installs b507199x0.dev(old devtools) and b507199x1.dev (old bootstrap). with only the old version of devtools(b507199x0.dev) installed, all calls to b507199x14(new devtools) from the current wrangler and devtools-api.js fail. This only effects registering rulesets, scheduling events and profile information on account webpage, which resolve after manual installation of b507199x14.

picolab/devtools should have its kre Authorize Client token, found in wrangler-config.js as "wrangler.clientKey", to be updated to install b507199x13.prod instead of b506607x15.prod with b507199x13.prod given proper system credentials. Or have b506607x15.prod source url updated to picolab/devtools bootstrap_prod.krl while keeping its same system credentials and update devtools code to use b506607x15.prod instead of b507199x13.prod. which solution should we implement?

[windley]

Why not use v1_devtools_bootstrap?

[burdettadam]

sounds good. ill make a pull request with that updated bootstrap rid.