Repository navigation
Verify retained coding results through an independent native ledger - #94
Merged
Conversation
added 30 commits
October 30, 2026 15:14
added 27 commits
October 31, 2026 21:25
…-linked-verification-authority-20261101
Require an exact published review and the same verified owner before one fresh linked-verification request. Keep current native host-admin proof separate from the mapped SCM actor; use the same request for uncertain readback and explain current linked results through typed facts. Preservation cut, not ready for main: the combined host cohort recorded 157 passes and one setup error at the real source-catalog free-space floor. An earlier isolated native-manager consumer passed, without transferring that proof. The final three-file ambiguity guard has Ruff/AST validation but has not been rerun through tests or mypy. No frontend inputs changed.
Revalidate the current pending conversation under native locks and bind its immutable intake digest to the grant. Recover typed current or unknown operation facts when interruption precedes the final reply marker, without repeating admission or substituting parent check history. Focused host regressions: 48 passed, prohibited effects zero; mypy eight modules and Ruff/format seven files passed. The known native-manager disk-floor fixture remains explicitly unexecuted on this cut. No frontend, API wiring, native service, qualification or runtime adoption change is claimed.
# Conflicts: # src/firefly_forge/linked_verifications.py
Append workspace_tools without shifting historical admission materials or changing membership. Keep historical/core hashes intact and declare the exact current additive authority tail. Exercise valid command indices above the old limit while retaining strict SDK refusals before HTTP. Reproduced all five owned Python CI failures, then passed the same nodes and 46 focused host cases with prohibited effects zero. Twenty-eight unrelated custody cases were not selected. Mypy one module and Ruff/format three files passed. Other hosted failures and fresh composed qualification remain separate.
Report only a closed-whitelist exception kind when initial best-effort observation fails. Preserve production one-second sampling, cancellation and recorded task state. Give the SQL custody fixture an explicit observation budget while keeping every predicate and revocation assertion intact. Deterministic host regressions reproduce missing diagnostics then pass all 31 observer cases with all six effect counters zero. Mypy one source module and Ruff/format three files pass. Actual PostgreSQL remains unexecuted; the original CI exception kind and timeout hypothesis are not proven.
This was referenced Nov 1, 2026
ancongui
merged commit Nov 1, 2026
997b91b
into
integration/crm-reconciliation-current-main-20261031
7 checks passed
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.
An accepted coding result can need fresh verification without replaying coding work. Add a native pyfly service, controller and worker with an independent hash-chained check ledger. The complete effective check list, exact source and current consent govern parent settlement; original claims, history and spent usage remain intact. Builds can refresh ignored output directories only after a known successful result and unchanged selected files, payload and Git index.
Natural-language GitHub confirmation is bound to the current published review and pending conversation. Interrupted admission reads the same durable request. Git delivery retains the exact SCM consent, QA actor locks and a final native transaction fence for authority, inputs, source and index. The PR also connects authorized source browsing and durable runner artifacts, supports elastic verification lists and refreshes the walkthrough.
Validation: 99 focused cross-lane host cases pass together; full Python type checking passes for 450 modules, with repository Ruff/format checks passing. Seven browser keyboard cases pass with explicit Code-tab focus and selection. The walkthrough has 694 refreshed captures. The current documentation passes a strict MkDocs build and discovery checks for 75 pages and 75 local Manrope social cards. Exact head
486696ccb982b8e283813c566d3de7dc9e2edfd2passed Verify 41333778963 across Python, Studio, container, documentation and aggregate checks; Documentation 41333779009 also passed. Actual current-source Native250/251 requests, all SQL201 cases in 12 drained packets, REG34/loader35 registration, installed App22 profile/RPC and a real installed native-UoW test passed. Native tool-boundary proof is not whole-controller production confinement. The current catalog has 202 MCP tools and 373 versioned templates. The focused host tests use controlled provider and persistence seams, with temporary Git repositories. The separately recorded physical PostgreSQL and installed-runtime gates above are exact 486696 proof; they do not establish live GitHub or completed product acceptance.Stacked on #93 and includes #86. The source PR contains no runtime deployment. The exact 486696 local artifact was qualified and adopted separately under Root ownership; source integration, public release and generated-product acceptance remain separate decisions. No cloud deployment is included.
Known product boundary: Original same-claim reconciliation is accepted at journal 361. One separate seven-check operation has four known successful commands and is held in needs_reconciliation, unknown=false, with no ordinal 5 intent. The original exception was not recorded; a controlled reproduction identified a selected untracked Vitest cache-file guard. Its source fix and the bot current-facts correction remain isolated and uninstalled. The latest real bot reply contradicted the accepted recovery and known results. No rerun, reset, replacement operation, new coding grant or new CRM commit/PR is claimed; acceptance remains 41/87. Source integration does not assert completed CRM end-to-end acceptance or authorize replay.