Skip to content

Release 1.11.0 - #73

Merged
rich0 merged 15 commits into
masterfrom
release/1.11.0
Jul 28, 2026
Merged

Release 1.11.0#73
rich0 merged 15 commits into
masterfrom
release/1.11.0

Conversation

@rich0

@rich0 rich0 commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Summary

Minor safety/reliability release from develop.

User-facing

Branch hygiene

  • Merged master into the release branch to absorb ruleset smoke commits; kept develop AGENTS.md content (history preserved, smoke content discarded)

Maintainer

  • Version bump via bump-version.sh 1.11.0
  • Ebuild rename 1.10.41.11.0
  • INVENTORY/DEPENDENCIES ebuild path sync

ChangeLog

Safety: Stage 3 and Stage 4 interactive merge tools receive disposable
/tmp views of non-live inputs (ancestor and/or Portage ._cfg* marker)
so accidental tool saves cannot corrupt permanent backups or markers
(issues #65, #68). Before promoting a staged marker to the Stage 2
ancestor (._new-cfg_*), validate its MD5 against Portage VDB CONTENTS
for the live path; mismatch skips promote with a warning, missing
CONTENTS fails open (issue #66). Docs: optional MentisDB guidance in
AGENTS.md (PR #70). Expanded Tier D path/hostile and Tier G CONTENTS
promote tests.

Checklist

  • ./scripts/check-version.sh 1.11.0 passes locally
  • perl -c cfg-update passes
  • ./test/run-tests.sh --full passes (252 passed)
  • CI integration check green on this PR

Post-merge

Maintainer checklist: issue #72

rich0 added 14 commits June 20, 2026 10:52
…ssue #65)

Pass disposable copies of the 3-way ancestor and Portage ._cfg* marker to
interactive merge tools so accidental saves on non-live panes cannot corrupt
permanent backups or markers. Live file and *.merge output paths stay real.

Also extends Tier D mocks/tests (hostile input overwrite, temp path checks)
and clarifies tool_intro for 3-way tools.
Drop file-scope $path_view_* globals. make_merge_view_temps takes basename
and real paths and returns the two view paths; cleanup takes those paths;
launch_tool_with_merge_view_temps keeps them as my locals and only rebinds
existing $path_backup_new/$path_new around launch_tool.
Replace the Stage-3-only pair API with make_merge_view_temp /
cleanup_merge_view_temp operating on one path. Stage 3 calls each twice.
Keeps a thin cleanup_merge_view_temps(@paths) convenience for 0-N temps.

Prepares for Stage 4 marker-only views (issue #68).
feature: Stage 3 merge tools use /tmp views of ancestor and marker (issue #65)
…stor promote (issue #66)

Before promoting a staged marker snapshot to ._new-cfg_*, compare its MD5 to
the Portage VDB CONTENTS digest for the live path (last-install BUILD_TIME).
Mismatch skips ancestor promotion with a warning; missing VDB fails open.
New helpers take all inputs via parameters/returns.
Capability-gated instructions so agents with MentisDB use chain
cfg-update automatically; agents without it skip the section.
docs: optional MentisDB memory guidance in AGENTS.md
…omote

feature: validate markers against Portage CONTENTS before ancestor promote (issue #66)
Reuse launch_tool_with_merge_view_temps so interactive 2-way tools
receive a disposable $TMPDIR copy of $path_new, not the real ._cfg*
marker. Live and *.merge paths stay real. Extend tool_intro, docs,
and Tier D path/hostile coverage.
feature: Stage 4 merge tools use /tmp view of Portage marker (issue #68)
Absorb master ruleset smoke history; keep develop AGENTS.md content
(MentisDB section and all prior develop guidance).
Bump version strings and ebuild PV to 1.11.0. ChangeLog covers Stage 3/4
merge-view temps (#65, #68), CONTENTS ancestor promote validation (#66),
and optional MentisDB AGENTS guidance. Sync INVENTORY/DEPENDENCIES ebuild
paths to the new PV.
Made more accessible to the end user and described in terms of actual impact.  Commit history still has the details of how it was done.
@rich0
rich0 merged commit 28e2fd7 into master Jul 28, 2026
1 check passed
@github-project-automation github-project-automation Bot moved this from Backlog to Done in Refactor/cleanup cfg-update Jul 28, 2026
@rich0
rich0 deleted the release/1.11.0 branch August 1, 2026 14:09
@rich0
rich0 restored the release/1.11.0 branch August 1, 2026 14:09
@rich0
rich0 deleted the release/1.11.0 branch August 1, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant