fix(reliability): v0.9.1 field hardening and IDEA authority persistence - #35
Draft
eybersjp wants to merge 22 commits into
Draft
fix(reliability): v0.9.1 field hardening and IDEA authority persistence#35eybersjp wants to merge 22 commits into
eybersjp wants to merge 22 commits into
Conversation
…ity, staleness, and command entry
… statement binding
…tability, exact statement equality, pure read-only resolution, and fail-closed recommendations
…ammar, and atomic state transitions
…IFIED scope, close public registration escape, complete transition matrix
…d decision authority, and complete transition matrix
…n authority records, and close supersession bypasses
…ity defaults, and enforce immutable resolution PODs
… and enforce sequential discovery
…on resolutions, fix supersession CLI imports, and prevent confirm replay
… nested state creation (Candidate 14)
…iscovery (Candidate 15)
…nstalled commands (Candidate 16)
…sh-chat restart resilience
…esolved design authority Move APPROVED stage check before checkpoint resume guard so approveCurrentIdeaBrief() always returns COMPLETE regardless of stale PENDING checkpoint. Add DESIGN_SYSTEM_SETUP staleness guard: if canonical design-system-state.json is no longer unconfigured, fall through to determineNextInteractionFromDiscovery. Extend INTERACTION_STATUSES with IN_PROGRESS and NOT_STARTED so validateWorkflowStructure accepts checkpoint statuses written by presentCurrentInteraction for non-interaction phases. All 82 v091-field-hardening tests pass. All 118 cross-suite tests pass. npm test and release:validate clean.
…c group consumption, crash recovery, and design-state truthfulness
- Close public authority API exports in runtime/orchestration/index.mjs - Complete PREPARED journal recovery binding exact target state and staged post-state - Add failpoint 4: after discovery persistence before journal finalization - Implement 4-tuple duplicate receipt detection with DK_INTERACTION_ALREADY_CONSUMED - Implement same-discovery receipt recovery before pending-interaction resume - Add Product Owner design applicability decision and protocol - Add advisory scope proposal step and interaction revision for scope adjustments - Deprecate single-candidate CLI operations in favor of idea-confirm-requirements - Full test validation: 87/87 field hardening tests, package consumer tests, and npm test passing cleanly
eybersjp
changed the title
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
1 participant
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.
Development status
Target: Development Kit v0.9.1
Branch:
fix/v0.9.1-field-hardeningPublished stable release:
v0.9.0PR status: Draft — engineering gates are green; live field acceptance is still required before merge/release.
Purpose
Harden the v0.9 Reliability Control Plane against authority bypasses, stale/resumed interaction errors, partial state writes, path/root ambiguity, and Product Owner provenance defects discovered through repeated independent review and field-oriented adversarial testing.
This patch deliberately keeps
package.jsonat0.9.0until the final release cut. The branch contains the candidate v0.9.1 implementation and release documentation, but v0.9.1 is not yet published.Current implementation
IDEA workflow authority and persistence
USER_STATED,AI_PROPOSED,RESEARCH_DERIVED, andASSUMEDcandidates.UNCLASSIFIEDremains explicit until Product Owner scope confirmation.Interaction integrity
expectedInteractionFingerprint.Crash-safe discovery state
discovery-journal.json.Design Authority truthfulness
Universal lifecycle entry and project-root authority
/dk-*workflows.process.cwd()guessing..agents/execution, symlinks, spaces, and cross-platform path handling are covered.Verification state
The current PR head has passed GitHub Actions CI.
Completed release-gate evidence on the branch includes:
npm run release:validatePASS.npm run doctorPASS.See
docs/08-maintenance-release/v091-release-checklist.mdfor the authoritative release gate.Remaining before merge/release
The engineering and documentation gates are complete. The following live field acceptance remains mandatory:
/dk-ideaworkflow in a clean scratch project with a human Product Owner.DK_INTERACTION_FINGERPRINT_MISMATCH.idea-approvelocks the approved brief and correctly unlocks/dk-spec.0.9.1, finalize the changelog release date, rerun release validation, merge, tag, publish, and verify npm/GitHub Release publication.Merge policy
DO NOT MERGE / DO NOT RELEASE while the live field acceptance items remain open.
The stable public line remains v0.9.0 until the final v0.9.1 acceptance and release gates are completed.