Skip to content

fix(ci): estate-wide foundational remediation - #23

Merged
hyperpolymath merged 2 commits into
mainfrom
fix-ci-estate
Jul 23, 2026
Merged

hyperpolymath merged 2 commits into
mainfrom
fix-ci-estate

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Fixes Validate Hypatia Baseline, root shape files, and tar slashes in release artifacts.

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
@hyperpolymath
hyperpolymath merged commit 4155329 into main Jul 23, 2026
28 of 34 checks passed
@hyperpolymath
hyperpolymath deleted the fix-ci-estate branch July 23, 2026 21:16
@sonarqubecloud

Copy link
Copy Markdown

hyperpolymath added a commit that referenced this pull request Nov 10, 2026
## Summary

Adds the v2 thin journal that STATE option B (ruled 2026-11-10) sends
the journal sections of STATE v1 to. You said it is just a file in the
repo, so this is that file: `docs/status/JOURNAL.adoc`.

## Changes

- **`docs/status/JOURNAL.adoc` (new).** The five STATE v2 fields from
`standards` `1-formats/templates/STATE.a2ml.v2.spec.adoc`: `phase`,
`last_action`, `next_action`, `session_marker`, `updated`, plus a
`Blockers` table. It is AsciiDoc, not the spec's `@state` block, because
A2ML is retired and no new `.a2ml` may be created.
- **`docs/practice/AI-CONVENTIONS.adoc`.** Session startup step 2 now
reads the journal, so agents actually use it. STATE v1 is marked legacy.
- **`anytype_chora.deed`.** Comments only: STATE's `[position] phase =
"implementation"` now has a home (the journal's free-text `phase`),
where the last PR left it as an open owner question. Milestones stay in
`ROADMAP.adoc`.

## Where each field came from

STATE v1 is months stale (2026-07-21), so the journal is checked against
primary sources, and the file has a `Provenance` section saying which is
which.

- `phase`: `ROADMAP.adoc` (Done list). The kernel has had no logic
change since 2026-07-21; one commit touched `src/kernel/`, a CI
remediation (#23).
- `last_action`: the merge commit of #73.
- `next_action` and the `tea-gate` blocker: **carried from STATE v1 and
not re-verified.** `session_marker` says so, and asks you to confirm.
- `state-archive-rewire` blocker: the archive step is blocked because
`openssf-compliance.yml`, the Must invariant, `validate-template.sh`,
the e2e test and the arrival-pack generator still require `STATE.a2ml`.

## Decision for you

The journal says it **governs over** STATE v1's journal sections where
they disagree, so the two don't double-track while STATE stays live.
That is my reading of option B. Say so if you want it worded
differently.

## RSR Quality Checklist

### Required

- [ ] Tests pass — N/A: docs and comments only.
- [ ] Code is formatted — N/A.
- [ ] Linter is clean — `deed_lint.js` reports OK on the deed.
- [x] No banned language patterns; no `unsafe`; no banned functions.
- [x] SPDX headers present on the new file.
- [x] No secrets, credentials, or `.env` files included.

### As Applicable

- [ ] `.machine_readable/6a2/STATE.a2ml` updated — not changed (see
above).
- [x] Documentation updated.

## Testing

- `deed_lint.js` → OK.
- Every path the journal cites exists.
- `scripts/check-root-shape.sh` and `scripts/check-no-md-in-docs.sh` →
PASS. No `.a2ml` created.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01J1XmMC49T8sZ3uUuvrgB7y)_

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant