[BUG] Native directory context publication rejects valid operation lifetimes #23

Closed
opened 2026-10-01 18:34:09 +02:00 by erikinkinen · 0 comments
Owner

Summary

Native exact-directory publication rejects valid enumeration and non-job metadata grants after successful provider acquisition because context installation requires the job-lifetime cwd purpose.

Reproduction

Source-derived reproduction, not executed: acquire a native exact directory through resolve_powerbox_object with ENUMERATE and an invocation lifetime, or READ_METADATA with an invocation lifetime. resolve_context_object prepares a directory context, publish_context_object publishes the original candidate, and set_cwd_context rejects the operation/lifetime. Existing native follow-up fixtures include these routes.

Expected and actual behavior

Expected: publish the independently retained directory with its exact requested operation and lifetime. Only job-lifetime directory metadata grants may act as job cwd; enumeration must remain restricted to its existing operations.

Actual in source: context installation returns DENIED, publication maps this to cleanup uncertainty, and the preparation is retired instead of returning the requested grant. Runtime adapters treat the uncertainty as fatal. No runtime reproduction or execution pass is claimed.

Environment and identity

  • Component revision: Vfsd 3f4a6414945914723dcd533ad90fb1db8782c199.
  • Integration runtime Vfsd selector: e4e6cb58bb639cbac326043e818e52054b084f7e; runtime adoption of the current migration remains pending.
  • Image/profile/toolchain: no image built or executed for this report.
  • Input route: authenticated namespace or live exact-directory endpoint, existing explicit enumeration/metadata purpose and requested lifetime.
  • Last known working revision: not established.

Evidence and prior checks

Source inspection of src/exact_objects/native.rs, src/cwd/native/publication.rs, src/handles_cwd.rs and src/exact_objects/native_followup_tests.rs. The directory context owns no additional grant; original counted scope custody and endpoint operation/lifetime checks must remain decisive. Tests/builds/CI observation remain deferred by instruction. Six positive, operation-negative, source-generation and cleanup controls are authored and unrun.

Tracking

Related: #16 and #3. Repair context installation against the actual retained root/candidate, preserve existing endpoint operation and job-cwd checks, and keep resolver derivation bound to the original source generation.

Implemented in Vfsd ea701c13, with manual documentation. Context installation now verifies original scope generation and complete retained root/current evidence. Exact operation and lifetime are preserved; the separate job-cwd predicate still governs reports and resolver-owned teardown. Resolver scopes no longer copy path/cwd metadata, and current source custody is reauthenticated before descriptive reads or cloning. Six controls cover nine original purpose/lifetime combinations, source-independent custody, closure/reuse, write attenuation, pending cleanup and context installation. Tests/builds/CI remain deferred; this is source completion under the testing waiver, not executed validation.

## Summary Native exact-directory publication rejects valid enumeration and non-job metadata grants after successful provider acquisition because context installation requires the job-lifetime cwd purpose. ## Reproduction Source-derived reproduction, not executed: acquire a native exact directory through `resolve_powerbox_object` with `ENUMERATE` and an invocation lifetime, or `READ_METADATA` with an invocation lifetime. `resolve_context_object` prepares a directory context, `publish_context_object` publishes the original candidate, and `set_cwd_context` rejects the operation/lifetime. Existing native follow-up fixtures include these routes. ## Expected and actual behavior Expected: publish the independently retained directory with its exact requested operation and lifetime. Only job-lifetime directory metadata grants may act as job cwd; enumeration must remain restricted to its existing operations. Actual in source: context installation returns DENIED, publication maps this to cleanup uncertainty, and the preparation is retired instead of returning the requested grant. Runtime adapters treat the uncertainty as fatal. No runtime reproduction or execution pass is claimed. ## Environment and identity - Component revision: Vfsd `3f4a6414945914723dcd533ad90fb1db8782c199`. - Integration runtime Vfsd selector: `e4e6cb58bb639cbac326043e818e52054b084f7e`; runtime adoption of the current migration remains pending. - Image/profile/toolchain: no image built or executed for this report. - Input route: authenticated namespace or live exact-directory endpoint, existing explicit enumeration/metadata purpose and requested lifetime. - Last known working revision: not established. ## Evidence and prior checks Source inspection of `src/exact_objects/native.rs`, `src/cwd/native/publication.rs`, `src/handles_cwd.rs` and `src/exact_objects/native_followup_tests.rs`. The directory context owns no additional grant; original counted scope custody and endpoint operation/lifetime checks must remain decisive. Tests/builds/CI observation remain deferred by instruction. Six positive, operation-negative, source-generation and cleanup controls are authored and unrun. ## Tracking Related: #16 and #3. Repair context installation against the actual retained root/candidate, preserve existing endpoint operation and job-cwd checks, and keep resolver derivation bound to the original source generation. Implemented in [Vfsd ea701c13](https://git.erikinkinen.fi/erix/vfsd/commit/ea701c13534e2406bb18c1461455df3129824a27), with [manual documentation](https://git.erikinkinen.fi/erix/docs/commit/b346d7b2a08b9a77afd994fae03cfffb8f701188). Context installation now verifies original scope generation and complete retained root/current evidence. Exact operation and lifetime are preserved; the separate job-cwd predicate still governs reports and resolver-owned teardown. Resolver scopes no longer copy path/cwd metadata, and current source custody is reauthenticated before descriptive reads or cloning. Six controls cover nine original purpose/lifetime combinations, source-independent custody, closure/reuse, write attenuation, pending cleanup and context installation. Tests/builds/CI remain deferred; this is source completion under the testing waiver, not executed validation.
erikinkinen 2026-10-01 18:34:09 +02:00
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:19 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/vfsd#23
No description provided.