Update actions.r
Update actions.r

Limiting __write__ to not allow object! makes sense if you're doing the open, write, close single use paradigm but reduces flexibility for working with schemes.  This is to allow an object! as data, and the role of the write actor will be to make it into the form for writing to the destination.
draegtun/ren-c,kealist/ren-c,codebybrett/ren-c,rgchris/ren-c,giuliolunati/ren-c,kealist/ren-c,rgchris/ren-c,giuliolunati/ren-c,draegtun/ren-c,draegtun/ren-c,rgchris/ren-c,kealist/ren-c,codebybrett/ren-c,codebybrett/ren-c,giuliolunati/ren-c,kealist/ren-c,giuliolunati/ren-c,hostilefork/rebol,hostilefork/rebol,codebybrett/ren-c,draegtun/ren-c,giuliolunati/ren-c,codebybrett/ren-c,hostilefork/rebol,hostilefork/rebol,kealist/ren-c,rgchris/ren-c,hostilefork/rebol,hostilefork/rebol,codebybrett/ren-c,draegtun/ren-c,kealist/ren-c,rgchris/ren-c,draegtun/ren-c