Repository navigation
Add issue reporting and verified release tracking - #7
Merged
Merged
Conversation
Retain suspected defects in a private report ledger shared by chat tools and the Reported issues view. Capture local evidence and investigate through agent-workflow before filing repository-native issues with dk-workflows. Keep publication intent durable so uncertain GitHub responses require reconciliation before another creation. Track investigation, issue closure, fix commits, published packages and observed installed versions separately. Ship the reporting skill in portable and Codex packages and extend checked release provenance with component versions and explicit fixed issues.
Keep the attention notice warning colors during hover so the generic button tint cannot make its text unreadable in the dark theme. Exercise the hovered state explicitly in the existing light and dark scans.
Keep accepted report evidence out of oversized process arguments and retain the active lifecycle across explicit recovery. Finalized unusable findings release investigation capacity and allow a fresh attempt. Preserve verified fix identities and versions across release failures. Keep loaded report pages through journal updates and verify issue link destinations at the host boundary.
Use native agent-workflow package evidence and a verified closing fix to establish dependency availability. Keep credential retry deadlines across reporting requests and restarts without affecting other provider traffic. Let completed investigations leave publication reconciliation pending while the queue advances. Keep selected report details current when reads overlap, and allow local fixture ports to avoid other checkouts.
Queue fresh investigation when new evidence misses an immutable worker snapshot, before stale findings settle or an unclaimed issue is created. Preserve claimed-effect reconciliation and known issue identity across publisher races. Redact cookie and identity-token credentials from reports and private diagnostics. Preserve live detail progress during journal updates, support closing-reference syntax, and reconcile scoped report controls with their canonical meanings.
Retain actionable state when publication is interrupted, and prevent old publishers from overwriting newer investigations or recovered issues. Reject private observations and recovery evidence inside source checkouts. Keep pagination usable through continuing refreshes and prove that an active fake provider times out and terminates. Reconcile behavior and UI assertions with the fixture verification.
Keep delayed publication results from replacing newer issue identities or outcomes. Preserve safe association of previously unrecorded effects. Treat failures proven before HTTP dispatch as recoverable rejection while retaining reconciliation for possibly dispatched creations. Bound and reap the interruption fixture's child process.
Redact complete Authorization and Proxy-Authorization values, including unknown schemes and structured proxy headers, before retained evidence, investigator input or issue publication can expose credentials. Release mutation controls after their own refreshed list renders while queued journal reads continue. Fetch publisher history so valid packages can verify older fix commits while preserving exact artifact promotion. Extend evidence, browser and delivery fixtures and map the assertions to the UI and reporting flow.
Keep the source tree and main-bound reconciliation receipts unchanged. The push check compares its actual before and after commits and runs the full fixture suites; the PR check retains the main comparison. Fold this temporary empty checkpoint into the guarded full-series cleanup. Preserve this tree and obtain fresh CI for the final regrouped head.
Redact Authorization and Proxy-Authorization arrays inside textual evidence while preserving adjacent fields across retention, investigation and publication. Keep the idempotency key when retrying the same uncertain submission. Give edited evidence a fresh key so it can be accepted without duplicating an earlier observation. Map the retry assertion to the evidence control and reporting flow.
Keep the source tree and main-bound reconciliation receipts unchanged. The push check compares its actual before and after commits and runs the full fixture suites; the PR check retains the main comparison. Fold this temporary empty checkpoint into the guarded full-series cleanup. Preserve this tree and obtain fresh CI for the final regrouped head.
Use one decoded traversal for header pairs and escaped MCP evidence. Preserve adjacent diagnostic fields and complete raw header redaction; bound decoding and redact unresolved text when limits are reached. Keep the existing submission and publication race assertions in owned child processes. Kill and reap stalled workers before removing their private fixtures, and update the reporting flow coverage mappings. Assert decoding exhaustion and exact large diagnostic integers.
Rebuild the embedded report UI after integrating main, and record successful fixture reconciliation against the current target.
dkropachev
force-pushed
the
feature/issue-reporting
branch
from
October 26, 2026 04:48
c3f7894 to
3dc19c3
Compare
Recognize X-Api-Key aliases and sensitive name/value header records across the existing evidence sanitization paths. Preserve exact JSON numbers during both sanitizer decoding steps. Extend the existing journal and attention capture assertions, and correct the reporting flow assertion descriptions.
Reuse existing credential recognition for client_secret in structured and textual evidence. Extend the capture fixture across retention, investigation and publication while preserving neighboring diagnostics. Correct the catalog descriptions for service rejection recovery and individual HTTP response classification.
Share operation-scoped authentication, conditional caching and persisted rate-limit cooldowns. Reuse matching PR commit evidence, batch release verification and reconcile report markers through a private incremental index with atomic generation checks. Preserve refresh schedules and uncertain-publication safeguards. Fixture assertions verify 73 cold and 62 warm inbox requests. Go race tests, all 18 specification reconciliations and make ci FLOW_BASE=main pass.
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.
Issue
Code Factory has no durable way to report suspected defects, investigate them with local runtime evidence, or follow their fixes through published releases. Chat observations and GitHub issue state alone cannot establish whether a fix is available or installed.
Fix
Add a private SQLite report ledger shared by six authenticated MCP tools and the Reported issues view. Submissions retain an idempotent observation immediately, then capture scoped local evidence and queue investigation through agent-workflow. The bundled reporting skill supplies host observations, and dk-workflows drafts repository-native issues after investigation establishes ownership within dk-code-factory.
Retain workflow admission and publication intent before external effects, reconcile uncertain GitHub creation by an opaque report marker, and expose missing-information and recovery controls. Investigation and filing use installed, authenticated dependencies without automatically installing or upgrading them.
Track processing, investigation outcome, GitHub closure, fix commits, stable and prerelease availability, and observed installed versions independently. Release tracking verifies published assets and checked component/fixed-issue provenance; missing evidence displays Unknown. Refreshes retain successful evidence with freshness and retry details.
Ship the reporting skill in portable and Codex packages, update daily-use guidance, and reconcile the glossary, UI registry and behavior contracts with implementation and assertions.
Decisions