stake_move

Performs native stake-program action `stake_move` for a GLAM vault.

Handler narrative

Load the GLAM state or program account required by the instruction and verify the signer.
Validate native staking permission, then apply the requested stake-account action through the Solana stake program.

The submitted accounts must match the declared account list, signer requirements, writable requirements, fixed program addresses, and account relationships shown below.
The GLAM state account is the source of truth for owner, enabled integrations, delegate permissions, policies, assets, borrowable assets, timelock settings, mint linkage, and pricing records.
The vault account must be the PDA controlled by the core protocol program and derived conceptually from the state account; instructions use it as the vault authority for SOL, token accounts, and external positions.
Owner-level actions must be signed by the state owner unless the instruction is explicitly an integration callback, mint-authority callback, delegate action, or emergency access update.

Account	Role	Description
glam_state	writable	State account owned by the GLAM Protocol program; it records vault configuration, policies, and pricing records.
glam_vault	writable	Vault account controlled by the GLAM Protocol program; conceptually derived from the state account and used as the vault authority.
glam_signer	signer, writable	Calling authority. It must be the owner or a delegate with the explicit permission required by this instruction.
cpi_program	read-only	External program invoked by this instruction.
source_stake	writable	Instruction-specific account supplied by the caller or SDK.
destination_stake	writable	Instruction-specific account supplied by the caller or SDK.

Argument	Type	Notes
move_stake	bool
lamports	u64

Enable native Stake Program access on GLAM Protocol staging builds. Protocol bitflag: 0b00000010; review status should be checked before production use.
Delegate permission: Stake Program Stake/Unstake depending account movement.

No additional cross-instruction constraint is documented beyond account initialization, authority checks, and policy validation.