Repository navigation
docs: synchronize SMV Injector v0.1.0 public milestone - #97
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 476a167f0d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - zero health reconnects; | ||
| - zero automatic Start events. | ||
|
|
||
| An independent capture spot-check contained 39,524 primary SV frames over approximately 9.881 seconds, an effective rate of approximately 3999.899 fps, zero observed `smpCnt` discontinuities, and ten 3999 -> 0 wraps. The capture matched the accepted P0 wire identity and retained `smpSynch=0`. |
There was a problem hiding this comment.
The only capture provenance given here spans approximately 9.881 seconds, but docs/SMV_STUDIO_RC2_ACCEPTANCE.md:17 requires at least 10 seconds of SV traffic and apps/arstack_studio/src/Rc2Acceptance.cpp:103-104 enforces the same threshold. Because the changed release documents mark P0.5 physical acceptance as accepted without listing this gate as deferred, this evidence cannot support the claimed acceptance; retain a capture spanning at least 10 seconds or explicitly revise/waive the gate before presenting the release as passed.
AGENTS.md reference: AGENTS.md:L263-L265
Useful? React with 👍 / 👎.
|
|
||
| This target runs the ARStack61850 Sampled Values injector on the current ESP32-P4 Ethernet development board using the internal EMAC and onboard RMII PHY. | ||
|
|
||
| > **Public product milestone:** the validated 4I+4V / 4000 fps path is released as stable [`v0.1.0`](https://github.com/masarray/arstack61850/releases/tag/v0.1.0). The broader runtime experiments documented below remain engineering follow-on work and do not expand the v0.1.0 claim boundary. |
There was a problem hiding this comment.
This stable-release banner still directs readers to docs/SMV_INJECTOR_STATUS.md as the current completion statement, but that document's lines 91-100 say trusted canonical capture, production packaging, and long-duration qualification remain unclaimed. Those capabilities are now declared completed in this README and the new release record, so embedded users receive mutually exclusive current status; update the linked document or label it historical and point readers to the v0.1.0 release record.
Useful? React with 👍 / 👎.
1 participant
Purpose
Synchronize repository documentation and public landing surfaces with the completed ARStack Studio / SMV Injector v0.1.0 stable public release.
Scope
Documentation only. No runtime, firmware, protocol, IED Simulator, or workflow behavior changes are retained in the final diff.
Updated surfaces:
README.mdpublic landing + current SMV milestone;apps/arstack_studio/README.mdproduct landing/download/checksum status;embedded/esp32p4_smv_injector/README.mdembedded landing and v0.1.0 claim boundary;docs/SMV_STUDIO_P0_RELEASE.mdfrom pre-release checklist to released milestone record;docs/SMV_STUDIO_V0.1.0_PUBLIC_RELEASE.mdimmutable public milestone/provenance page;docs/FEATURE_MATRIX.mdSMV publisher/public-product status;PROJECT_HANDOFF.mdcurrent production/release handoff.Release truth synchronized
v0.1.0;9c7fc7300220db4643e5643081240b955cfe12df;d9b5b6848415c7e6d1c52ec929e57c66b608058d;missed=0,txFailures=0,healthReconnects=0,automaticStarts=0;smpSynch=0boundary;IED Simulator PRs #75/#82 are explicitly kept as separate product tracks and are not modified by this PR.