Record post-submission runtime evidence

docs/codex-for-oss-application.md

@@ -10,6 +10,10 @@ Prepared: 2026-07-22
 
 Official form rechecked: 2026-07-22
 
+Submission reported complete: 2026-07-24
+
+The maintainer reported that the application was submitted. The ChatGPT-account email, OpenAI Organization ID, confirmation page, and exact submission timestamp remain private and are not stored in this repository.
+
 ## Recommendation
 
 Submit in **English**, even through the PT-BR form. OpenAI publishes no language requirement and no evidence that language changes selection odds. English is recommended only to reduce translation friction for a global technical review.
@@ -100,6 +104,8 @@ Use these links only if OpenAI requests verification; the form has no dedicated
 - CI history: <https://github.com/domfelipe/vibeflow-n8n/actions/workflows/ci.yml>
 - Launch discussion: <https://github.com/domfelipe/vibeflow-n8n/discussions/3>
 - Public r/n8n feedback that shaped v0.9: <https://www.reddit.com/r/n8n/comments/1v3is1w/i_built_an_opensource_safety_gate_for_aigenerated/>
+- Public runtime feedback and anonymized-corpus offer: <https://www.reddit.com/r/n8n/comments/1v3is1w/comment/ozbyh0f/>
+- Recorded static/runtime evidence boundary: <https://github.com/domfelipe/vibeflow-n8n/blob/main/docs/community-launch-v0.9.md#post-release-runtime-feedback--2026-07-24>
 - Engineering PRs: <https://github.com/domfelipe/vibeflow-n8n/pulls?q=is%3Apr+is%3Amerged>
 
 ## Evidence snapshot
@@ -118,6 +124,18 @@ Captured on 2026-07-23 after release:
 
 Do not describe maintainer PRs, the maintainer's own workflow, clones, or unattributed stars as external adoption.
 
+## Post-submission evidence snapshot
+
+Captured on 2026-07-24:
+
+- an external Reddit commenter publicly validated the static-preflight/runtime-observability split;
+- the commenter reported fail-open Code execution, error-as-data, and AI-output truncation cases from a community-workflow corpus;
+- the commenter offered to run anonymized failing workflows through Vibeflow and share false positives;
+- the linked Pisama node and runtime project were independently verified, including their separate MIT and fair-code licensing boundaries;
+- no workflow fixture, false-positive result, PR, contributor relationship, partnership, or integration had been received or established at capture time.
+
+This is evidence of substantive community engagement and a prospective evaluation path, not evidence of adoption or contribution.
+
 ## Confidentiality boundary
 
 Do not submit or link the full real-workflow audit. Application materials must not include:
@@ -139,10 +157,11 @@ The approved public description is: **“a real, production-scale 92-node conver
 - [x] All narrative answers are under 500 characters.
 - [x] Real-workflow evidence is anonymized.
 - [x] Early adoption is described honestly.
-- [ ] Insert the exact ChatGPT-account email.
-- [ ] Insert and verify the OpenAI Organization ID.
+- [x] Supply the exact ChatGPT-account email privately in the form; do not retain it in the repository.
+- [x] Supply the OpenAI Organization ID privately in the form; do not retain it in the repository.
 - [ ] Re-read the current Program Terms immediately before submission.
 - [ ] Save the confirmation page and submission timestamp privately.
+- [x] Application submission reported complete by the maintainer on 2026-07-24.
 
 ## After submission
 

docs/community-launch-v0.9.md

@@ -16,6 +16,26 @@ The v0.9 scope came from the public [original r/n8n launch thread](https://www.r
 
 Captured on 2026-07-22: the thread had 3 votes and several substantive comments. Treat the comments as product evidence; do not present the vote count as broad adoption.
 
+## Post-release runtime feedback — 2026-07-24
+
+Reddit user [`Fit_Preference_1795`](https://www.reddit.com/r/n8n/comments/1v3is1w/comment/ozbyh0f/) publicly described the runtime counterpart to Vibeflow's static checks and offered to test anonymized failing workflows against Vibeflow. The report identified three failure classes:
+
+- a `continueOnFail` Code node crash that leaves the execution marked successful;
+- an error object flowing through an item's JSON as ordinary data;
+- truncated AI output reaching downstream nodes despite valid JSON and a successful node status.
+
+The commenter also noted that intentional token caps must be distinguished from accidental truncation to avoid false positives. These cases reinforce the product boundary: Vibeflow can detect deterministic fail-open configuration or require a structural completeness guard, but it cannot observe runtime output or prove that an alert is watched.
+
+The linked [`n8n-nodes-pisama`](https://github.com/Pisama-AI/n8n-nodes-pisama) community node is MIT-licensed and forwards execution telemetry. Runtime detection is implemented by the separate, self-hostable [`pisama-n8n`](https://github.com/Pisama-AI/pisama-n8n) service under a fair-code license. Its public [July 2026 corpus campaign](https://github.com/Pisama-AI/pisama-n8n/blob/main/eval/campaigns/2026-07-guard-campaign.md) records 70 committed workflows, 67 real executions, and 19 observed-and-detected failures. The comment's 69-workflow report and the repository campaign are different snapshots and must not be combined into one metric.
+
+Evidence status at capture time:
+
+- verified: substantive public technical feedback and a public offer to provide anonymized false-positive evidence;
+- not yet verified: receipt of the workflows, Vibeflow verdicts, false-positive count, or a shared interoperability contract;
+- not claimed: partnership, external contribution, external user adoption, or a shipped Pisama integration.
+
+The smallest useful follow-up is three anonymized cases: fail-open Code execution, error-as-data, and intentional versus accidental truncation. A new Vibeflow rule should be added only when paired unsafe/safe fixtures expose a deterministic static signal.
+
 ## Reddit — r/n8n
 
 ### Title