8 Commits

  • core: log AGENTS.md paths as URIs (#28989)
    ## Why
    
    No need to do path contortions when it's for our own logs.
    
    ## What
    
    Follow up on a previous PR's nit and update the path-types skill for
    future reference.
  • Record more path migration guidance for codex. (#28851)
    Some common themes pulled out of both human and automated reviews from
    the last couple of days' migrations to `PathUri` and
    `LegacyAppPathString`.
  • Tell codex to avoid changing rollout format. (#28632)
    Just adds a requirement to the path-types skill to nudge Codex away from
    touching rollout types while migrating paths.
  • Revert "Tell codex about PathUri serde compat. (#28595)" (#28627)
    This reverts commit bd2a786326, which
    didn't capture all the nuance we need for this migration.
  • Tell codex about PathUri serde compat. (#28595)
    This addresses another wrinkle I keep having to re-prompt codex about
    when migrating to cross-OS paths.
  • Record invariants for path migration. (#28589)
    ## Why
    
    Help Codex understand how to execute the migration to support cross-OS
    paths.
    
    ## What
    
    Expand the path-types skill with our goals and constraints.
  • Clarify model-generated and legacy app path types (#28577)
    ## Why
    
    `ApiPathString` kind of implies that it can be used anywhere we pull a
    path out of JSON, but it's not really appropriate for tool arguments
    when the model might generate relative paths.
    
    Prefer `String` for model-generated paths and we can handle the
    conversion per feature for now and define a shared abstraction later if
    it makes sense.
    
    # What
    
    Rename `ApiPathString` to `AppLegacyPathString` to clarify its role.
    
    Expand the `path-types` skill to tell the model to leave tool args as
    bare strings.
  • [codex] add path-types skill (#28347)
    ## Why
    
    Codex contributors and agents need repository-scoped guidance for
    choosing compatible Rust types
    for operating system paths during the ongoing URI migration. Keeping the
    guidance in the repository
    makes the app-server and exec-server rules available consistently
    without relying on a personal
    skill installation.
    
    ## What
    
    - Add the `path-types` skill at `.codex/skills/path-types/SKILL.md`.
    - Document the intended uses of `ApiPathString`, `PathUri`,
    `AbsolutePathBuf`, and `PathBuf` across
      protocol, internal, and shared dependency boundaries.
    - Keep migrations of existing types limited to explicit requests and
    proportional edits.
    
    ## Validation
    
    - Validated the skill structure with skill-creator's
    `quick_validate.py`.