Export an agent configuration for a reviewed platform migration

Why use this

1. An assistant owner changing platforms may want familiar identity settings and schedules without carrying credentials or incompatible behavior into the new environment. A successful export does not establish that the destination interprets those settings the same way.

2. A secrets-free migration manifest could identify portable content, unsupported fields and owner decisions before import. Schedules and permissions would remain proposed on the destination until the owner checks their meaning and authorizes activation.

Why an agent / simpler alternative

Useful judgment

Separate portable preferences from platform-specific configuration and identify risky or ambiguous fields.

Simpler alternative

Recreate a few settings manually when the existing setup is small.

Unsuitable when

The export cannot be reviewed for secrets or destination behavior is undocumented.

Proposed inputs

1. Name

   Approved configuration selection

   Owner

   Owner

   Minimum scope

   Identity text and schedule definitions explicitly selected for migration

   Quality check

   Exclude credentials, private tokens and unrelated conversation content.

2. Name

   Destination field description

   Owner

   Owner or platform maintainer

   Minimum scope

   Supported import fields and schedule semantics

   Quality check

   Check time-zone handling and unsupported configuration types.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only redacted configuration and an offline export manifest.

Compatibility unknowns

1. Unknown: exact runtime, export/import formats and destination interpretation of identities or schedules.

External actions requiring approval

1. Exporting sensitive content, importing settings or activating destination schedules and access.

Expected deliverable and review checks

Proposed artifact

Reviewable migration archive plan with included fields, exclusions and destination-mapping questions.

Critical checks

1. No credentials or access-granting secrets are included.

2. Schedule timing and authorization are reviewed rather than blindly inherited.

Missing output evidence

No new workflow run or output inspection was performed for this overlay.

Failure signals and proposed responses

1. Signal

   A schedule field embeds an authentication token.

   Why it matters

   The archive could expose persistent access.

   Proposed response

   Exclude the secret and require an approved destination-authentication process separately.

2. Signal

   A destination interprets an unspecified time zone differently.

   Why it matters

   Migrated tasks could run at unintended times.

   Proposed response

   Require explicit time-zone confirmation before activating any schedule.

Effort and cost — unknown

Setup work

1. Inventory selected settings and define a redaction/mapping checklist.

Ongoing review

1. Inspect the archive and verify destination behavior in separately authorized work.

Unknowns

1. Unknown: format support, import effort and semantic compatibility.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

An invented configuration manifest contains a credential-labelled placeholder and a schedule without a time zone.

Acceptance checks

1. The credential field is excluded.

2. The schedule cannot be marked ready for activation.

Stop conditions

1. Real secrets, import authority or persistent-access changes are required.

Limits

1. Editorial migration preparation; manifest review is not proof of a safe or successful platform import.