docs: use relative paths to READMEs
MODIFY
README.md
README.md
@@ -37,9 +37,9 @@ easy to program, and easy to reason about integrity. CapTP frees the
programmer from needing to create bespoke communication protocols over message
ports or byte streams.
-[SES]: packages/ses
-[Handled Promise]: https://github.com/Agoric/agoric-sdk/tree/master/packages/eventual-send
-[CapTP]: https://github.com/Agoric/agoric-sdk/tree/master/packages/captp#agoriccaptp
+[SES]: packages/ses/README.md
+[Handled Promise]: packages/eventual-send/README.md
+[CapTP]: packages/captp/README.md#agoriccaptp
[LavaMoat]: https://github.com/LavaMoat/LavaMoat
[POLA]: https://en.wikipedia.org/wiki/Principle_of_least_privilege
[supply chain attacks]: https://en.wikipedia.org/wiki/Supply_chain_attack

MODIFY
packages/compartment-mapper/README.md
packages/compartment-mapper/README.md
@@ -561,6 +561,6 @@ type ModuleParameter = string;
> the same purposes, using a tool called TOFU: _trust on first use_.
[LavaMoat]: https://github.com/LavaMoat/lavamoat
- [Compartments]: https://github.com/endojs/endo/blob/master/packages/ses/README.md#compartment
+ [Compartments]: ../ses/README.md#compartment
[LavaMoat]: https://github.com/LavaMoat/lavamoat
[package entry points]: https://nodejs.org/api/esm.html#esm_package_entry_points

MODIFY
packages/far/README.md
packages/far/README.md
@@ -8,7 +8,7 @@ It exists to reduce the boilerplate in Hardened JavaScript vats that are running
in Agoric's SwingSet kernel,
[`@agoric/swingset-vat`](https://github.com/Agoric/agoric-sdk/tree/master/packages/SwingSet),
or arbitrary JS programs using Hardened JavaScript and communicating via
-[`@endo/captp`](https://github.com/endojs/endo/tree/master/packages/captp).
+[`@endo/captp`](../captp/README.md).
You can import any of the following from `@endo/far`:

MODIFY
packages/import-bundle/src/compartment-wrapper.md
packages/import-bundle/src/compartment-wrapper.md
@@ -77,5 +77,5 @@ except that it could not make such an invocation itself, because it won't have a
- [Compartments]: https://github.com/Agoric/SES-shim/blob/master/packages/ses/README.md#compartment
- [SES]: https://github.com/Agoric/SES-shim/blob/master/packages/ses/README.md
+ [Compartments]: ../../ses/README.md#compartment
+ [SES]: ../../ses/README.md

MODIFY
packages/lp32/README.md
packages/lp32/README.md
@@ -7,4 +7,4 @@ with Uint8Arrays.
These streams are "hardened" and depend on Hardened JavaScript.
Most JavaScript environments can be locked down with the
-[SES shim](https://github.com/endojs/endo/blob/master/packages/ses/README.md).
+[SES shim](../ses/README.md).

MODIFY
packages/ses/error-codes/SES_NO_DOMAINS.md
packages/ses/error-codes/SES_NO_DOMAINS.md
@@ -18,4 +18,4 @@ These domain properties are unfrozen, so they can be used for covert
communication between tenant programs, and provide a view into dynamic scope
that any program can directly manipulate to confuse other programs.
-[domainTaming]: https://github.com/endojs/endo/blob/master/packages/ses/lockdown-options.md#domaintaming-options
+[domaintaming]: ../docs/lockdown.md#domaintaming-options

MODIFY
packages/ses/src/error/README.md
packages/ses/src/error/README.md
@@ -75,7 +75,7 @@ However, the above description violates one of our constraints: The automatic lo
This section explains our *plans* to build a logging experience on top of this system that supports local and distributed asynchrony. Also tracked at [Support deep stacks for local asynchronous log-based debugging #1862](https://github.com/Agoric/agoric-sdk/issues/1862) and [Support distributed deep stacks for log-based debugging #1864](https://github.com/Agoric/agoric-sdk/issues/1864).
JavaScript itself is not a dustributed language, but it is a highly asynchronous language. Our distributed computational model&mdash;communicating event loops&mdash;pushes much of our code into making heavy use of this asynchrony. For such code, individual synchronous call stacks are often short and uninformative. [Causeway](https://github.com/Agoric/agoric-sdk/issues/1318#issuecomment-662127549) shows that the asynchronous and distributed analog of synchronous stack traces is a directed acyclic graph of prior causal events, each with their local synchronous stack at their moment of causation. To capture this well requires instrumenting the promise system in ways impossible for user code. However, the most important causal paths are
- * the [eventual-send](https://github.com/tc39/proposal-eventual-send) operations by [handled promise](https://github.com/Agoric/agoric-sdk/tree/master/packages/eventual-send), whether expressed by `E()` or `~.`.
+ * the [eventual-send](https://github.com/tc39/proposal-eventual-send) operations by [handled promise](../../../eventual-send/README.md), whether expressed by `E()` or `~.`.
* the `.then` operation. However, we replace the builtin `Promise.prototype.then` at our peril. Many built in operations implicitly invoke the original binding of `Promise.prototype.then` in ways we cannot override. However, our same eventual-send package already provides a safer alternative `E.when` operation.
Restricting the instrumentation to these two operations gives predictability and preserves platform independence, but at the loss of some useful diagnostic information. This loss may encourage programmers to shift from their current habits to eventual-send and `E.when`, which would be a good thing anyway.

docs: use relative paths to READMEs