Skip to content

Research: define exact-workspace platform boundary #10

Description

@joaomj

Parent map: #1

Decision to resolve

Which repository structures, filesystem entry types, and metadata are included in TinyHarness exact undo across supported platforms?

Inputs

Questions

Cover submodules, nested repositories, sparse checkout, special files, symlinks, executable bits, ACLs, xattrs, hard links, case behavior, and empty directories.

Output

A fail-closed support matrix and portable exactness contract.

Resolves when

TinyHarness can state exactly which workspaces it accepts and what exact restoration means on each supported platform.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    researchPrimary-source investigation that resolves a decisionwayfinderDecision map and wayfinding work

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions