Master's unreleased ptc-bootstrap-protocol guide already covers protocol
version 3, so the scoped-repl format, the PtcProgramFormat member and the
dsh-ssh bootstrapHash step join it instead of a second guide. Re-record the
README, Note and guide translation pairs after the rebase.
With replScoped: true, persistent-in-memory runs each call as a separate
VM Script in one retained context. Each call starts with copies of the
top-level bindings left by earlier calls, so a later call may declare any
earlier name again with any keyword while earlier functions and
still-running code keep their values. Results, top-level await, errors
and asynchronous failures follow the existing REPL evaluator; modules
load only through dynamic import(), resolved from the environment's first
working directory.
The control protocol moves to version 3; the upgrade guide covers
preinstalled bootstraps and the new PtcProgramFormat member. The Agent
Note records the decision and its comparison with node:repl and
vm-script, and the ptc-scoped-repl snapshot pins the model guidance.
- ForgeActionFailure gains `unknown` for an answer that does not confirm
the outcome; the GitHub provider passes it on instead of `failed`, the
panel Remote refuses with `forgePanel/action-unknown`, a viewed mark
stays, and the other actions ask the reader to check the browser.
- Reruns skip workflow runs with a pending check, try every finished run,
and report the refused ones together; the card offers a rerun only when
a failed check's run has finished.
- Review requests resolve users and teams to node ids and call
`requestReviews`, which GitHub Enterprise Server 3.19 and 3.20 have;
bots still go through `requestReviewsByLogin`.
- Viewed marks are kept per change request and head, so a reread at the
same head keeps writes in flight and their locks, and paths named after
object properties read only their own entries.
- The reviewer search never chooses from the listing of an earlier query.
- Documentation states the unknown code, the branch update evidence, and
the `canBeRebased` approximation, and drops stray blank lines.
The forge subsystem page gains the overview and viewed mark types and
contracts, and the generated Cordis, configuration, and event catalogs
follow the new service methods and the maxViewedFiles option.
ChangeRequestSnapshot now carries the reviewers, linked closing issues,
branch update methods, and the viewer's rights to request reviews and
rerun checks; each check names its rerun. Providers may implement viewed
mark reads and writes, failed check reruns, review requests with a
reviewer search, and head-pinned branch updates. The registry fails an
action a provider lacks without polling, and polls a watched change
request after every action the provider answered.