feat: compose independent work SCM CI and knowledge drivers (#105) #111
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-105-independent-provider-drivers"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #105, active AC1-6. Current head
6c7c2d0a(full SHA in PR metadata), base/merge-baseb1c9ffca16f06596e5c3afdca3b9893cf7422d8d. Four normal owner commits, no history rewrite. Seven of ten independent whole-PR review invocations consumed; no current approval. Review1 infrastructure failure, reviews2–7 COMMENT; previous actionable findings were corrected without resetting history.Review7 found the new opaque identity parser's length limit rejected valid long supplementary-Unicode subjects produced by its own encoder. Latest commit derives the parser bound from the complete canonical envelope, all maximum-length fields, worst-case JSON Unicode escaping and hex expansion. Existing canonical bytes are unchanged. A red-first maximum-size combined-field test now proves round-trip and oversized refusal.
Final closed/offline
make check package-check auditpassed on current content: 2,385 tests, 85 existing native opt-ins skipped, 106 subtests, 1063.48s; static/types/import/secrets/diff gates, reproducible builds, installed mixed-driver/Forgejo/recovery/compatibility journeys and audit all passed. A synthetic test-storage artifact initially triggered the secret scanner; its generated file was removed and remaining test artifacts preserved outside the checkout, then the complete gates reran successfully with no scanner suppression. CI for the new head is pending.The implementation retains independent Jira/GitHub/Jenkins/Confluence and exact-Git knowledge bindings, retained Forgejo facade, provider-qualified opaque identities, explicit trusted grants, exact intent/fence/recovery and bounded native effects. Unsupported native operations refuse. No live provider accounts/effects, production credentials, new dependency/ADR, external repository mutation, release or deployment.
Independent review6 verified exact pinned Jenkins Core and Git plugin source/license using public source clones. Review7 independently verified those plus exact versioned official GitHub OpenAPI, but could not independently read the Jira GET-issue contract because the official reader response was oversized and access to a locally prepared public snapshot was denied. This remains an infrastructure evidence gap, not approval. A fresh whole-PR independent review and exact-head current CI/currentness are required before merge and separately verified acceptance.
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.