diff --git a/docs/development.md b/docs/development.md index ec70dfd..fb62924 100644 --- a/docs/development.md +++ b/docs/development.md @@ -69,192 +69,16 @@ Accepted decisions: - [Match registered records during resolution inspection](adr/0021-sequence-resolution-correspondence.md) - [Bind companion contexts after main selection](adr/0022-main-relative-context.md) -For cross-cutting changes, follow every applicable row. Completed implementation -and remediation plans are preserved in Git history at `cb5b435`; use current -contracts and the component overview for ongoing work. For example: - -```sh -git show cb5b435:docs/roadmap/remediation.md -``` +For cross-cutting changes, follow every applicable row. Use current contracts +and the component overview for ongoing work. Release-candidate, publication, and verification work follows the operational [release procedure](release.md). Its module-selected ReleaseKit `publish` invocation validates the committed candidate and publishes only the intended tag; those release checks remain distinct from the everyday development check. -The completed string-and-integer schema-version implementation and remediation -records are preserved in Git history at `244104f`. The -[configuration contract](config.md#application-schema-versions) owns current behavior. - -The completed source-origins and public-facade roadmaps, implementation plan, and -resolved review findings are preserved in Git history at `5760614`, for example -`git show 5760614:docs/roadmap/remediation.md`. The earlier source-origins staged -plan remains at `28e7fc5:docs/roadmap/implementation.md`. Current resolution -behavior belongs to the [configuration contract](config.md#recorded-application-resolution), -and current facade ownership belongs to the [component overview](internal/overview.md). - ## Baseline validation -The completed typed result-value and focused inspection roadmap, implementation -plan, and resolved review findings are preserved at `174e030` under -`docs/roadmap/`. Current behavior belongs to the [configuration contract](config.md) -and the public declaration comments; [ADR 0024](adr/0024-compare-inspection-views-across-application-types.md) -records the inspection comparison decision. - -The completed main-relative companion roadmap, Audita request, implementation -plan, and remediation report are preserved in Git history at `47547bc` under -`docs/roadmap/`. The [layered loading contract](config.md#layered-loading) -describes current behavior, and [ADR 0022](adr/0022-main-relative-context.md) -records the context binding decision. - -The completed field-level sequence resolution roadmap, implementation plan, and -resolved audit findings are preserved in Git history at `7e53863` under -`docs/roadmap/`. For example: - -```sh -git show 7e53863:docs/roadmap/implementation.md -git show 7e53863:docs/roadmap/remediation.md -``` - -The [configuration contract](config.md#recorded-application-resolution) owns -current resolution behavior, and [ADR 0021](adr/0021-sequence-resolution-correspondence.md) -records the correspondence decision. - -The completed filesystem-source and underlay roadmap, original feature request, -implementation plan, and resolved remediation record are preserved in Git history -at `b604aa1` under `docs/roadmap/`. Current behavior belongs to the -[configuration contract](config.md#layered-loading). Built-in sibling -inheritance is now part of the [configuration contract](config.md#sibling-inheritance). -The completed request, roadmap, plan, and resolved review findings are preserved -in Git history at `83c59ea` under `docs/roadmap/`. - -The completed overlay rename plan and release-workflow simplification record are -preserved in Git history at `73ce6e9` under `docs/roadmap/`. Current overlay -behavior belongs to the [configuration contract](config.md#selected-overlays), -and release operations belong to the [release procedure](release.md). - -The completed ReleaseKit adoption, startup performance request and experiments, -benchmark evidence, performance audit, implementation plan, and remediation -record are preserved in Git history at `8e91a2b` under `docs/roadmap/`. For example: - -```sh -git show 8e91a2b:docs/roadmap/startup-benchmark.md -``` - -Remaining optimization candidates belong to -[future performance experiments](roadmap/future.md#3-performance-experiments). - -The completed effective-configuration diff roadmap, implementation plan, and -resolved review findings are preserved in Git history at `1c2610c` under -`docs/roadmap/`. The -[configuration contract](config.md#effective-configuration-diffs) owns current -comparison and disclosure behavior, and -[ADR 0010](adr/0010-effective-configuration-diff.md) records the decision. - -The completed input-destination, relative-import-destination, and shared -source-version roadmaps, associated consumer request, implementation plan, and -resolved review findings are preserved in Git history at `e4270c9` under -`docs/roadmap/`. For example: - -```sh -git show e4270c9:docs/roadmap/implementation.md -git show e4270c9:docs/roadmap/remediation.md -``` - -Current behavior belongs to the configuration contract's -[input destinations](config.md#input-destinations), -[imports](config.md#explicit-imports), and -[shared source-version checks](config.md#shared-source-version-checks) sections. -Explicit sequence-item placement, collection operations, identity registration, -and final registered-identity validation are owned by the -[strict composition](config.md#strict-document-composition) section; -[imports](config.md#explicit-imports) owns acquisition and scheduling. The -[maintained sequence catalog](consumers/README.md#identified-prompt-sequences) -shows the consumer boundary, and [ADR 0017](adr/0017-collection-sequence-policy.md) -records the collection decision. - -The completed sequence-composition roadmap, implementation plan, and resolved -remediation record are preserved in Git history at `008d2ba` under -`docs/roadmap/`. For example: - -```sh -git show 008d2ba:docs/roadmap/sequence-composition.md -git show 008d2ba:docs/roadmap/implementation.md -git show 008d2ba:docs/roadmap/remediation.md -``` - -The completed import-discovery roadmap, implementation plan, and resolved -remediation record are preserved in Git history at `5747ec4` under -`docs/roadmap/`. For example: - -```sh -git show 5747ec4:docs/roadmap/imports.md -git show 5747ec4:docs/roadmap/implementation.md -git show 5747ec4:docs/roadmap/remediation.md -``` - -The subsequent import-integration audit and completed remediation record are -preserved at `6903c9e:docs/roadmap/remediation.md`; retrieve them with -`git show 6903c9e:docs/roadmap/remediation.md`. - -The completed sequence-identity/collection-policy roadmap and implementation -plan are preserved in Git history at `d0a605a`: - -```sh -git show d0a605a:docs/roadmap/sequences.md -git show d0a605a:docs/roadmap/implementation.md -``` - -Current behavior belongs to the configuration contract's -[strict composition](config.md#strict-document-composition), -[sibling inheritance](config.md#sibling-inheritance), and -[CLI overrides](config.md#explicit-cli-overrides) sections. -The completed remediation record, including the algorithm-audit findings, is -preserved at `ea46001:docs/roadmap/remediation.md`. - -The completed configuration-discovery roadmap, implementation plan, and -remediation record are preserved in Git history at `0369111`, for example -`git show 0369111:docs/roadmap/remediation.md`. Current behavior belongs to -[configuration discovery](config.md#configuration-discovery); the public -[discovery declarations](../discovery.go) own the Go API. - -The completed consolidation proposal, implementation plan, and resolved audit -findings are preserved in Git history at `34cbc0d` under `docs/roadmap/`. For -example: - -```sh -git show 34cbc0d:docs/roadmap/implementation.md -git show 34cbc0d:docs/roadmap/remediation.md -``` - -Potential enhancements are tracked in [future features](roadmap/future.md). -The completed audit-remediation, internal-boundary simplification, shared-history, -and public API cleanup roadmaps, reviews, and resolved findings are preserved at -`68400ff` under `docs/roadmap/`. For example: - -```sh -git show 68400ff:docs/roadmap/api.md -git show 68400ff:docs/roadmap/remediation.md -``` - -Their earlier completed implementation plans are preserved at -`bb5540b:docs/roadmap/implementation.md` (audit remediation), -`f6d54a0:docs/roadmap/implementation.md` (internal-boundary simplification), and -`07e4ae5:docs/roadmap/implementation.md` (shared history). The plan at -`68400ff:docs/roadmap/implementation.md` records the public API cleanup. -Current behavior and migration information belong to the -[configuration contract](config.md), public declaration comments, and -[consumer guide](consumers/README.md#pre-v1-public-api-cleanup). - -The consolidated audit, including -findings, evidence, and settled scope decisions, is preserved at -`453da68:docs/roadmap/audit.md`; the original nine reports are preserved at -`ecd5d5d` under `docs/roadmap/`. Retrieve the consolidated record with: - -```sh -git show 453da68:docs/roadmap/audit.md -``` - Install the Go version required by `go.mod` or a compatible newer toolchain. Acquire declared dependencies explicitly before entering an offline development or validation environment: