docs: add investor-grade risk register with mitigations and evidence links - #146
docs: add investor-grade risk register with mitigations and evidence links#146CollinsKRO wants to merge 11 commits into
Conversation
|
@CollinsKRO is attempting to deploy a commit to the karagoz's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@CollinsKRO Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
Thanks for the risk register. The content is aligned with issue #94: it links from README/data room, is explicit about unaudited status, and includes concrete owner/action fields across the register. I cannot merge yet because whitespace validation fails:
reports trailing whitespace in
Please remove those trailing spaces. After that, I can re-run |
|
Thanks for the update. I rechecked the merge ref as Good news: the previous whitespace blocker is fixed now:
I still cannot merge yet because two evidence links in
The actual coordinator files appear to be |
|
I've bee trying to resolve this issue but the toggle bar isn't clicking. is there anything I can do about it? |
|
pls review this |
- Remove duplicate getMetrics method from orders-repo.ts - Fix timelock ordering in coordinator tests (dstTimelock < srcTimelock) - Add missing mock exports in App.test.tsx for getCurrentNetwork/getContractAddresses/getFaucets
soroban-env-host 22.x requires ed25519-dalek >= 2.0.0 unbounded; without a lockfile cargo resolves 3.x which breaks the env-host testutils build and the Soroban CI job. Pin 2.2.0 via the committed lockfile and stop ignoring it.
Newer stable (1.97+) breaks cargo install --locked stellar-cli 22.8.1 (ethnum 1.5.0 transmute error), failing the Soroban CI job. Pin to 1.96.1, the last version compatible with the pinned soroban-sdk 22.x stack.
updated_at is second-granularity (strftime %s now), so comparing two orders timestamps directly flakes when a second boundary falls mid-test. Assert the actual invariant (array sorted by updatedAt DESC) instead.
Use non-null assertions for the sorted-updatedAt loop indices so tsc --noEmit passes in CI.
2 participants
closes #94