docs: point the README verification section at the green CI run

The Validate workflow is green again on main after the audit overrides
refresh and the bus ledger test fix; record the run id instead of the
stale 2026-07-15 entry. Also note the fix under Unreleased.
This commit is contained in:
Evandro Fonseca Junior committed 2026-09-14 08:32:10 -03:00
1 parent 0852274102
commit a9364a344a
2 files changed
+2 -1

No files matched your search

+1
View File
@@ -5,6 +5,7 @@
- **Security overrides refreshed** — `protobufjs` `7.6.4` → `7.6.6`, `undici` `8.5.0` → `8.10.2`, and a new `brace-expansion` `5.0.9` override keep `npm audit` at 0 vulnerabilities; the `validate` gate (`typecheck` → `test` → `audit` → `pack:check`) passes again.
- **README rewritten** to the repository audit standard: verified install/build/test commands, the real `omp install` syntax, omp agent-directory resolution, and an explicit limitations section.
- **Release notes extraction fixed** — the `0.22.0-evandro.1` fork section promoted from `###` to `##` so `.github/workflows/release.yml` can build release notes for tag `v0.22.0-evandro.1`.
- **Bus ledger test made timing-independent** — `tests/bus.test.ts` no longer assumes the first bus envelope reaches the server within a fixed 5 ms, which failed on a slower CI runner (`0 !== 1`). The `Validate` workflow is green again on `main`.
## 0.22.0-evandro.1 — Evandro Fonseca Junior fork (oh-my-pi-telegram)
+1 -1
View File
@@ -218,7 +218,7 @@ Everything below was executed in this repository on Node 24.20.0 / npm 11.19.0 (
| `omp install <local path>` | exit 0, `Linked @evandrodevbr/oh-my-pi-telegram from .` (the link was reverted afterwards to leave the machine as it was) |
| `omp install --link <path>` | fails: `Unknown option '--link'` (kept out of this README) |
The test suite is deterministic and offline: transport calls are injected, so no live Telegram bot is required. The live Telegram paths (long polling, Rich Messages, Threaded Mode threading) are not exercised here beyond the CI history of `main` (last `Validate` run: success, 2026-07-15).
The test suite is deterministic and offline: transport calls are injected, so no live Telegram bot is required. Live Telegram paths (long polling, Rich Messages, Threaded Mode threading) are covered by the operator's own smoke sessions, not by this suite; the `Validate` workflow (npm ci + `npm run validate` on Node 24) is green on `main` (run 34838605928, 2026-09-14).
## Current state and limitations