Release v3.3.1

Summary

Two defects in how the ai and init commands treat an installed corpus, both silent: one installs a profile's skills without its rules, the other edits the corpus itself. Fixes #154 and #155.

Fixed

• cratis ai install and update resolve rules against the composed profile closure instead of the literal configured list, so a profile that reaches an application profile through composes gets that profile's rules and not just its skills — cratis/full/csharp was installing twelve application profiles' skills while dropping vertical-slices.md, reactors.md, react.md and the rest of the frontend set (#154).
• cratis init no longer writes through the symlinks cratis ai install creates. File.Exists follows a link, so appending the @CHRONICLE.md reference or writing the generated skill landed inside .cratis/ai — reported afterwards as corpus drift that cratis ai update refuses to replace without --force. Each destination is now resolved, following a link on the file or any ancestor directory, and reported as managed with a pointer to cratis ai update (#155).