Repository navigation
docs(release): v0.70.0 live-verification ledger, with the character-create rows corrected - #709
Merged
Merged
Conversation
Release step 4b evidence, written before the cut and indexed. Nine live runs on a migrated account plus five exit-code corrections verified on the real CLI, in the five-layer format (file count, magic bytes, dimensions, structlog invariants, a user-confirmable artefact). The decisive proof for the headline feature is semantic, not structural: two hand-drawn reference images went into `video r2v` and the clip came back carrying the same marker strokes, face and paper texture. Structural layers pass either way; only that separates "Flow bound the reference" from "Flow accepted and ignored it". Also records the four-beat two-character piece produced end to end (19.000s, 1280x576, clip_qa ok, A/V +0.000s) and, as corrections: `-o <existing directory>` now exits 2 in 0.8s instead of exit 1 after ~2min AND a billed orphaned clip; `character create` on a moved account exits 36 immediately instead of a bare RuntimeError exit 1 after a 20s wait. Four items recorded as NOT verified rather than omitted: * #692's original failure could not be reproduced. The reporter's own re-run was on a build WITHOUT the fix, so it shows the failure is intermittent, not that the fix works. * Flow CHARACTER entities were never exercised: `character create` cannot run on any account available here. * image / scene / movie / extend all exit 36 on the migrated host and no unmoved account exists here. * #699's sign-in-interstitial fidelity question has no bundle evidence. NOT committed to develop directly: the shared checkout was switched to another session's branch mid-flight, which is the v0.68.0 hazard the release skill documents. Parked here so nothing is lost. Refs #683, #692, #639
The ledger recorded the bug as the fix. Its exit-code table presented `character create` on a moved account exiting 36 as a v0.70.0 improvement, and its not-verified list said CHARACTER entities "cannot run on any account available here". Both were false, from one root: a 20 s readiness timeout was read as proof the feature does not exist on flow.google.com, and #701 then added a guard that aborted before probing the DOM — which made the claim unfalsifiable, because no run could look. #703 disproved it. The editor is fully present on the migrated host, on the same labs tRPC + aisandbox backend; only the view layer differs (React + Slate vs Angular + ProseMirror). Replaces both statements with what was actually run: a complete character on ci-probe — name, personality, voice, portrait and body, two distinct workflow ids, two distinct media ids, both images on disk with different checksums, confirmed by read-back. Plus `--model` determinism over four alternating runs and the orphan-rollback A/B (1 -> 2 entities without the fix, 2 -> 2 with). Records what was NOT verified rather than omitting it: the labs.google path for all seven changed anchors, since every account here is migrated. Also updates the #692 entry with evidence that changes what that issue is. flow.google.com CAN mint a reCAPTCHA Enterprise token: on /project/<id> the enterprise script and site key are present and a mint returns a 2404-char token, while the root grid carries no script at all. The mint runs on the pooled bootstrap page, which after the handoff IS the root grid — which is exactly why the reporter's bundle showed route: "/". So "any mint failure on a migrated page yields exit 36" refuses the host rather than fixing the cause. The probe and its write-up are deliberately not linked from here while they sit on the spike-skill branch: `check_doc_links.py` does not cover this file, so a cross-branch reference would have shipped dangling with every gate green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The v0.70.0 live-verification ledger, plus the correction that #703 forced.
The ledger recorded the bug as the fix. Its exit-code table presented
character createon a moved account exiting 36 as a v0.70.0 improvement, and its not-verified list said CHARACTER entities "cannot run on any account available here". Both were false, from one root: a 20 s readiness timeout was read as proof the feature does not exist onflow.google.com, and #701 then added a guard that aborted before probing the DOM — making the claim unfalsifiable.Replaced with what was actually run on
ci-probe:Kael Ridge Full— patched, not "Untitled Character"Algenib5698df21…, mediaca5732c9…, 633 976 Bde846b9c…, media247eec3b…, 449 397 B60975a89…vs60a27f39…Plus
--modeldeterminism over four alternating runs, and the orphan-rollback A/B (1→2 entities without the fix, 2→2 with).Also updates the #692 entry with evidence that changes what that issue is:
flow.google.comcan mint reCAPTCHA —/project/<id>carries the enterprise script and returns a 2404-char token, while the root grid carries no script at all, and the handoff leaves the pooled bootstrap page exactly there. That is why the reporter's bundle showedroute: "/".Records what was NOT verified, rather than omitting it: the labs.google path for all seven anchors #703 changed, because every account here is migrated.
Test plan
check_doc_links.py,check_repo_hygiene.pygreendocs/INDEX.mdconflict resolved as a union — both the new spike-recon link and the ledger's evidence reference are present, not one overwriting the othercheck_doc_links.pydoes not coverLIVE_VERIFICATION_*files — so it would have shipped dangling with every gate green