Skip to content

Pair a gateway as an environment that serves and never reads (slice I of #252, part 1a) - #744

Merged
Varuas37 merged 3 commits into
mainfrom
claude/project-thread-q3nib0-i-env-pairing
Oct 11, 2026
Merged

Varuas37 merged 3 commits into
mainfrom
claude/project-thread-q3nib0-i-env-pairing

Conversation

@Varuas37

@Varuas37 Varuas37 commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Requested by Saurav · project thread

Part 1a of slice I (#706) of #252.

Before: an owner could pair a phone (it acts as the owner and reads) or a peer gateway (its own principal, reads only what it is shared). There was no way to say "this machine may run agents for me". Any credential that could reach the gateway as a peer could, if shared with, read.

After: pairing.create {"enrollee":"environment"} creates a third kind of invitation. It uses the same one-use code, listener and PAKE. Approving it issues a credential that names the same gateway:<key hex> principal a reading peer would, and holds environment.serve and nothing else. A machine paired this way can never read a conversation, and no person, agent or integration can ever hold environment.serve. Nothing accepts a connection as an environment yet. That is part 1b, which waits on slice D (#737) because both touch the SSH link and env-serve files.

Why a credential and not a config entry

Whether a machine may serve this gateway is a fact about credentials, so the registry is its one authority. It is revoked like every other credential, and slice I's later parts re-check it at connect time and on every grant. A config map would be a second copy that could disagree with the registry.

How

  • Auth domain.
    • New action environment.serve. PrincipalKind::may_hold lets only a gateway hold it. A gateway may hold the read and serve actions, and never the conversation authority's.
    • ConsentClass::PeerEnvironment (peer-gateway-environment-serve). ConsentClass::grant is now the one place that decides which grant a class hands out. The intent, the disclosure check and the stored pairing all ask it.
  • Owner admission. The owner still needs credential.manage. They need to hold the proposed grant only when the class delegates their own grant (delegates_owner_grant). No person can hold environment.serve, so for an environment invitation that check is skipped.
  • Registry.
    • validate_grants now takes the principal's kind and asks may_hold. That one check covers every issuing path (credential.issue, bootstrap, owner recovery) and every open.
    • credential.issue of environment.serve to anyone is refused with Conflict, and nothing is written.
    • A stored registry where an environment credential also reads, or a person's credential serves, does not open.
    • The pairing record stores class: "environment". The client's private file uses its own magics (NSEP/NSEA), so existing device and peer files stay byte-for-byte unchanged.
  • Cedar. environment.serve is allowed only to active members holding the exact grant.
  • Server.
    • pairing.create maps the new enrollee.
    • conversation.share refuses a credential that does not hold conversation.read on this gateway's own resource (share_target_not_paired). Otherwise a share to an environment would record a reader that can never read.
  • Protocol. PairingEnrollee gains environment, and the Rust and TS types are regenerated.
sequenceDiagram
    participant Owner as Owner surface
    participant GW as Gateway (pairing runtime, Auth registry)
    participant Worker as Worker gateway (enrolling client)
    Owner->>GW: pairing.create {enrollee: "environment"}
    GW->>GW: owner holds credential.manage (not the serve grant: no person can)
    GW->>GW: ConsentIntent(class = PeerEnvironment, grant = ConsentClass::grant = environment.serve)
    GW-->>Owner: code (shown once), class peer-gateway-environment-serve
    Worker->>GW: Hello / Begin / Confirm (same listener, class bound in the PAKE)
    Owner->>GW: pairing.approve (exact key)
    GW->>GW: validate_grants: may_hold(Gateway, environment.serve)
    GW->>GW: credential gateway:<key hex>, grant environment.serve only, bound to the key
    GW-->>Worker: Active {credential, receiver, epoch}
    Owner->>GW: conversation.share {credentialId: the worker's}
    GW-->>Owner: share_target_not_paired (it holds no conversation.read), nothing granted
    Note over GW,Worker: Part 1b: the worker dials out and serves leases on this credential
Loading

Design row I1 in docs/design/auth/peer-gateways.md lists the tests. These are the new ones:

  • owner_route_creates_an_environment_invitation
  • an_environment_enrollment_issues_the_peer_principal_holding_only_serve
  • an_environment_is_paired_but_never_shared_with, which runs a full native-listener enrollment
  • cedar_allows_serving_only_to_a_member_holding_the_grant
  • each_class_discloses_only_its_own_grant

The member and admin refusal tests now run for every enrollee.

What this does not do

These are later parts of #706:

E enforces no tool-policy ceiling. Today the dialing side accepts only a reading enrollment.

Known limit, accepted by the owner on 2026-10-11. The registry records an environment pairing's class only once. If something rewrites both the class and the credential's grant on disk in the same consistent way, open accepts the result. Open still refuses any change to only one of the two. A writer that can change both can already add a stronger credential.

Checks

  • Local runs of fmt, clippy (-D warnings), the node check scripts, prettier, and the nessa-auth, nessa-protocol and nessa-client-core tests are all green. The nessa-server tests are green apart from the two below, and the nessa-local-storage tests apart from the first.
  • Three tests failed in this sandbox, all in code this PR does not touch. The sandbox runs as root, which ignores file permissions; that is the likely cause, but only the first was re-run on main.
    • nessa-local-storage unix::tests::*: also fails on main here.
    • managed_runtimes::use_admission_and_release_acknowledgement… ("an unwritable use journal admitted a generation").
    • codex::status_cleanup_removes_descendants….
      CI is the check that counts for these.
  • pnpm frontend:check had two failures: both script tests need just, which this sandbox does not have. smoke-auth passed.
  • Two internal review rounds; every finding is fixed.
  • CI is green on 5aae600. local-auth (windows-latest) passed on one re-run after an unrelated SDK timing test failed once.

Scripted gateway checks

Not run. This change adds a pairing class, with no UI, ACP or MCP behaviour, and it is covered by the native-listener enrollment test above.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EL5rzp9FLsixdtkMSbgffp


Generated by Claude Code

… of #252, part 1a)

The owner can now create an environment invitation with
`pairing.create {"enrollee":"environment"}`. It runs the same one-use
pairing on the same listener. What it issues names the peer gateway
principal and holds `environment.serve` alone, so a machine paired to run
agents can never read a conversation.

- Auth: a new `environment.serve` action that only a gateway principal may
  hold. A third consent class, `PeerEnvironment`. `ConsentClass::grant` is
  the one owner of which grant a class hands out. Owner admission asks for
  the owner's own grant only when the class delegates it. `validate_grants`
  asks `may_hold` on every issuing path and on open. The Cedar policy allows
  it to active members.
- Server: `pairing.create` maps the new enrollee. `conversation.share`
  refuses a credential that cannot read.
- Protocol: `PairingEnrollee` gains `environment`; generated types are
  regenerated.
- Docs: the "Environment peers" section and row I1 in peer-gateways.md, and
  read-grants.md.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EL5rzp9FLsixdtkMSbgffp
The socket fixture answers every share target with the caller's snapshot,
which held no conversation.read, so the new check refused its device.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EL5rzp9FLsixdtkMSbgffp
@coderabbitai

coderabbitai Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 5d504956-3770-47d9-9442-29961f371df5


📥 Commits

Reviewing files that changed from the base of the PR and between 17b78d8 and 5aae600.



📒 Files selected for processing (4)
  • crates/nessa-server/src/conversation/application/read_grants.rs
  • crates/nessa-server/src/product/read_access.rs
  • crates/nessa-server/tests/conversation/passive_read.rs
  • crates/nessa-server/tests/device_pairing/infrastructure/protected.rs


Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 7 remain after this review.




📝 Walkthrough
📝 Walkthrough

Walkthrough

Adds environment-peer enrollment with an environment.serve grant, class-specific registry validation, and Cedar authorization. Conversation sharing now requires the target credential to hold conversation.read on the caller’s gateway.

Changes

Environment Peer Enrollment

Layer / File(s) Summary
Consent and protocol contracts
crates/nessa-auth/src/domain/*, crates/nessa-auth/tests/domain/pairing/*, crates/nessa-protocol/src/product/generated.rs, crates/nessa-protocol/tests/pairing/wire.rs, protocol/product/v1.json
Adds the PeerEnvironment consent class and its environment.serve grant. Updates enrollee and consent-class protocol representations. Tests cover class parsing, grant validation, and wire round-trips.
Enrollment and registry validation
crates/nessa-auth/src/application/pairing/admission.rs, crates/nessa-auth/src/adapters/local/registry*, crates/nessa-auth/src/adapters/pairing/private_state*, crates/nessa-server/src/product/pairing.rs, crates/nessa-server/tests/device_pairing/owner_routes.rs, packages/nessa-client/src/presentation/pairing-api*, docs/design/auth/peer-gateways.md
Routes environment enrolment to PeerEnvironment, persists the class, and validates grants against principal kind. Admission checks credential.manage for the gateway and checks the proposed grant only when the consent class delegates an owner grant.
Serving authorization
crates/nessa-auth/src/adapters/cedar/*, crates/nessa-auth/tests/cedar_flow.rs
Adds the environment.serve Cedar action and a permit rule for active members. Tests cover grant, resource, role, and membership conditions.
Conversation-sharing boundaries
crates/nessa-server/src/conversation/application/read_grants.rs, crates/nessa-server/src/product/read_access.rs, crates/nessa-server/tests/conversation/passive_read.rs, crates/nessa-server/tests/device_pairing/infrastructure/protected.rs, crates/nessa-server/tests/product/socket/subscriptions.rs, docs/design/auth/peer-gateways.md, docs/design/read-grants.md
Requires a share target to hold conversation.read on the caller’s gateway. Tests cover environment credentials and grants scoped to another resource.

Priority: ➖ Normal

Estimated code review effort: 4 (Complex) | ~45 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant Owner
  participant PairingCreate as pairing.create
  participant AuthorizePairing
  participant LocalRegistry
  Owner->>PairingCreate: Request environment enrolment
  PairingCreate->>AuthorizePairing: Check credential.manage on gateway
  PairingCreate->>LocalRegistry: Publish PeerEnvironment pairing
  LocalRegistry-->>PairingCreate: Store class-specific grant
Loading


Merge Risk: ⚪ Minimal · up to 5aae6

The environment enrollment and gateway-scoped sharing changes have no established issue requiring resolution before merge.

Security Architecture Review

Security architecture risk: 🔵 Low · up to 5aae6

Serving permission remains separate from reading permission, and enrollment still requires owner authorization. No new access escalation was identified in the reviewed paths. Downgrade compatibility and serving connections planned for later work limit confidence beyond this enrollment change.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

  • inferred — The introduced authority is scoped to an approved credential, its organization, and the enrolling gateway resource. Possession of an environment credential does not supply conversation.read or credential.manage in the inspected authorization paths. A separate reading credential for the same gateway principal remains a distinct capability, so the guarantee should not be interpreted as preventing that machine from ever reading.

Trust Boundaries and Controls

  • observed — The enrolling party cannot select a different grant merely by relabeling the consent class: disclosure and public intent validate the class and canonical grant, and activation derives the gateway principal from the claimed key. Authorization checks the exact credential snapshot rather than unioning permissions by principal. Sharing additionally checks the requested credential and gateway-scoped read grant; the environment integration test asserts rejection with no persisted conversation grant.

Resilience and Maintainability Implications

  • observed — Enrollment transitions preserve revision-bound admission and exact intent ownership, reject reservation replay and claims against unavailable invitations, and bind cleanup to the credential, receiver, request, and epoch. Active cancellation revokes the credential in the durable mutation, and subsequent credential verification rejects revocation. These controls prevent repeated or interrupted enrollment from silently creating additional authority in the inspected state machine.

Pre-merge checks | Passed 4 | Failed 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage Warning Docstring coverage is 77.94% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 68 functions across 25 files. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Title check Passed The title clearly and concisely describes the primary change: pairing a gateway as an environment that can serve but never read.
Description check Passed The description explains the change, design, scope, tests, validation results, known limitation, and scripted gateway-check status. It includes the required Scripted gateway checks section and clearly…

  • Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Commit to this branch
  • Create a new PR





🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR



  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

Copy link
Copy Markdown
Contributor Author

@codex review


Generated by Claude Code

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-11T08:37:43.492608Z 17b78d8 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 17b78d882f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@Varuas37
Varuas37 marked this pull request as ready for review October 11, 2026 08:29

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 17b78d882f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

A registry answer whose conversation.read grant is on another resource of
the same organization no longer counts: the share is refused
share_target_not_paired, as Codex found on #744.

Part of #706.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EL5rzp9FLsixdtkMSbgffp

Copy link
Copy Markdown
Contributor Author

local-auth (windows-latest) failed on 5aae600 in a single test, nessa-sdk infrastructure::session_storage::ownership::tests::stopped_executor_input_drop_fault_keeps_slot, with physical fault subprocess watchdog expired (tests.rs:455). The failure came about 1,480 s into the SDK suite. This PR touches no nessa-sdk file. The test runs a fault subprocess under a wall-clock watchdog, which is the same pattern as the other load-sensitive Windows tests that have failed late in the suite on PRs that don't touch them. All 1,957 nessa-server tests passed in that same job. No fix exists yet. I'm re-running the failed jobs once. If it fails again I'll treat it as real.


Generated by Claude Code

@Varuas37
Varuas37 merged commit bae7a07 into main Oct 11, 2026
19 of 21 checks passed
@Varuas37
Varuas37 deleted the claude/project-thread-q3nib0-i-env-pairing branch October 11, 2026 15:43
Varuas37 added a commit to nessalabs/skills that referenced this pull request Oct 17, 2026
## Motivation

The recovered October9–12 ADR audits are the remaining source evidence
deferred by [#23](#23). Most of
their lessons already live in the ADR reconciliation procedure added by
[#22](#22): decision acceptance
is separate from delivery, slices need their own evidence, inventories
need lifecycle placement, and stale claims must be repaired wherever
readers encounter them.

One useful distinction can be clearer: a feature name is not proof that
the shipped design satisfies the decided contract. A different mechanism
may preserve the guarantee, leave a real implementation gap, or require
an explicit decision revision. This draft makes that comparison explicit
without prescribing the historical proposal as the correct design.

## Solution

1. `8a72865`: amend the existing ADR scope-reconciliation paragraph to
compare promised guarantees and distinguish an implementation gap from a
decision needing explicit revision.
2. `8a72865`: add one Core Rule2 example that links to that owner; keep
all historical project detail here.

Only two existing documentation files change. This is a narrow
clarification, so package/plugin versions remain `0.6.0`; the repository
requires bumps for broad changes. No new skill, duplicate audit
checklist, workflow, implementation, ADR file or issue is introduced.
**Leave this PR as a draft; do not merge without separate approval.**

### Baseline and source access

- Based on the actual default `wip` at
`572b154685a75892b54d939e1d2d9b0e6fb22477`, the merged #23 tree. Root
`AGENTS.md`, the engineering ownership table, ADR, architecture, method
and review owners were inspected. No additional applicable `.agents`
instructions were present.
- No competing open skills PR was found before editing. Earlier skills
issues are older Rust research, not a new ADR integration.
- Input is the recovered historical report-message evidence supplied
with this task. Full thread text was not accessible in this executor;
ZIP issue-body attachments remain unavailable. Neither original issue
drafts nor publication receipts are claimed inspected.
- Read-only public source checks inspected relevant PR metadata and
excerpts of the ADR index, runtime ADR, Read-grants design and
physical-persistence design at the October12 snapshot. These corroborate
the bounded mechanism comparison; they are not a fresh audit of current
Nessa.

### Source-to-owner dispositions

| Recovered finding family | Disposition | Existing owner / reason |
| --- | --- | --- |
| 501 linked once with unique identity but absent from lifecycle table |
Already covered | ADR inventory structure requires repository-consistent
placement and says a stray link is not index coverage. Uniqueness and
membership are separate checks already expressed. |
| 252 acceptance versus implementation checklist and tracking state |
Already covered | ADR scope reconciliation separates accepted decisions,
shipped slices, evidence and remaining gates; reader-surface repair
includes tracking issues. |
| Partial replay, grants, artifacts, pairing and outbound delivery |
Already covered | Per-slice evidence and gates; one merged
implementation does not establish full scope. |
| A proposed Cedar/semantic-record design versus the shipped metadata
grant table and durable journal | **Small amendment** | ADR scope
reconciliation now requires matching the promised guarantee instead of
the feature name and distinguishing implementation gaps from explicit
decision revisions. It does not decide which design is right. |
| Stale 0008/0009/202/302/392 prose, index/body conflicts and 688/689
status | Already covered | ADR contradiction repair covers header,
current prose, tables, checklists, index, README and tracking issue;
placement follows the repository convention. |
| Persistence mechanics and 27 ordering cases without decision
rationale/rejected alternatives | Already covered | ADR template
requires the binding constraint, alternatives and reasons; method's
decision artifact also includes rejected options. Implementation
instructions and reported tests are not newly relabeled as decision
history. |
| PR715 already addressed replay documentation; avoid filing it again |
Already covered | ADR's existing issue/open-PR comparison checks the
exact changed sections, not document overlap. No Nessa issue action is
taken. |
| Repeat-audit baseline/delta and outcome separation | Coverage
practice; no additional skill rule | Pin historical revisions and report
new/still-open/reconciled findings in this ledger under existing
evidence-class rules. A publication failure is not proof inspection
never completed. |
| Reported publication failures and disabled ADR automation | Reported
operational outcome only | No independent automation-state verification,
schedule change or publication retry. Rust research state is outside
this patch. |

### Recovered-report coverage ledger

These are historical findings at the stated revisions, not claims that
the defects remain in current Nessa. Repeated themes are counted once as
transferable guidance.

| Report message | Historical Nessa snapshot | Recovered coverage and
disposition |
| --- | --- | --- |
| October9 · `2a086b87-e13b-43af-a099-4a2f577bcd82` |
`4d1b7278cfe633a6c38094f0bcfb45d4d5043af0` | Reported 36 records:23
done/13 todo;326/344 moved done,252 accepted with implementation
separately tracked. 0008,202/302,392,501 and persistence-rationale
findings map to existing owners; no duplicate replay-doc work. |
| October10 · `2d3f1bcd-f54a-4d96-b836-3caa1a19e0b9` |
`88f34e4dabdeca46486dfbd5294e0a2a00a0a5fa` |501 membership,715 stale
replay index and720 unchecked grants slice are already covered. The
proposed-versus-shipped semantic-contract distinction supports the sole
amendment; peer738 and persistence rationale remain historical case
evidence. |
| October11 · `e4ad69af-9798-4d6f-a666-3a3dbb8aad70` |
`bae7a073b597285823b92f037d7079cf4522a716` | Reported 38 records:23
done/13 todo/2 root;688/689 still under review after739,744 pairing
shipped while748 outbound was not yet merged at this snapshot. Existing
lifecycle/slice/revision rules cover these distinctions. |
| October12 · `a452f573-d4e0-4663-a720-3970e6313f15` |
`07799e6405812a52297c02bac39525ec0315568e` | Reported37 further commits
and38 records; grant/artifact/lease work advanced while checklists
lagged;392,501 and rationale gaps persisted. Already-covered themes
reinforce the narrow clarification. Reported ADR automation disabling is
separate from audit completion and Rust research. |

Provenance: recovered messages belong to conversation
`6aba0796-656c-83e8-a735-49b9ed36b026`. The identifiers preserve source
attribution without putting private conversation links into reusable
skills.

**Unavailable attachments:** issue-body ZIP attachments were not read,
so exact unpublished drafts, their complete acceptance language and
publication outcomes were not independently reconstructed.
**October13–16:** no report messages were found by the recovery; these
dates are not counted as inaccessible completed reports. There is no
basis here to invent additional audit runs or claim a current Nessa
audit.

### Public supporting evidence

- At the [October12 runtime ADR,
sliceG](https://github.com/nessalabs/nessa-agent/blob/07799e6405812a52297c02bac39525ec0315568e/docs/adr/todo/252-runtime-roles-and-execution-leases.md#implementation-plan),
the wording names a Cedar grant. The [same-revision Read-grants
design](https://github.com/nessalabs/nessa-agent/blob/07799e6405812a52297c02bac39525ec0315568e/docs/design/read-grants.md#what-this-slice-does-not-do)
explicitly distinguishes its metadata table/journal from in-stream
semantic records and policy-bundle changes.
[#720](nessalabs/nessa-agent#720) is the
delivered slice. This is evidence to compare contracts, not proof that
every mechanism difference is a defect or that a chosen implementation
must be reverted.
- The [pinned ADR
index](https://github.com/nessalabs/nessa-agent/blob/07799e6405812a52297c02bac39525ec0315568e/docs/adr/README.md)
and [#715](nessalabs/nessa-agent#715),
[#739](nessalabs/nessa-agent#739) support the
historical projection/lifecycle examples; those rules already exist.
- [#744](nessalabs/nessa-agent#744) merged at
the October11 report's exact snapshot,15:43UTC.
[#748](nessalabs/nessa-agent#748) merged later
at16:37UTC. “Not yet merged” is a snapshot observation, not a current
outbound-delivery defect.
- [#652](nessalabs/nessa-agent#652) and its
[pinned physical-persistence
design](https://github.com/nessalabs/nessa-agent/blob/07799e6405812a52297c02bac39525ec0315568e/docs/design/bounded-physical-persistence.md)
support the distinction between implementation mechanics/reported tests
and a decision's rationale. This draft makes no new current missing-ADR
claim.

### Validation and limits

- **Run:** repository-wide local Markdown path and heading-anchor
validation:182 links pass (fenced template examples excluded).
- **Run:** all six declared skill paths, required frontmatter and agent
descriptors checked; package/plugin versions both remain `0.6.0`.
- **Run:** `git diff --check`; refreshed `origin/wip` remains at the
stated base before publication.
- **Run:** author diff review and independent source-to-owner triage,
followed by independent review of the final diff and this description.
No material blockers, duplicate owner or evidence/coverage overclaims
found.
- **Read-only source checks:** the public PRs and pinned documents
linked above resolved; selected historical excerpts were inspected. This
does not establish runtime behavior or an exhaustive current audit.
- **Unavailable:** original full thread text in this executor and ZIP
issue-body attachments. The supplied recovered-message evidence is
distinguished from source excerpts inspected here.
- **Not run:** runtime/native tests, historical ordering cases,
benchmarks, installed-skill behavioral evaluation or production defect
reproduction. No CI workflows or standard checked-in skill validator
exist in this repository; the documentation checks above were run
locally.

No `nessa-agent` files, issues, PRs or schedules were changed; the
separate #953 task was untouched. Prior denied issue publications were
not retried. No native/runtime tests, ordering cases or historical audit
checks were rerun. The change teaches a review distinction; it does not
assert a runtime-validated result or repair historical Nessa defects.
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.

2 participants