For #1: we don't want to do a script editor in the foreseeable future for two reasons - firstly, for HTML5 it would be snippets of Javascript, so suppose everyone uses snippets of javascript in all their games. If we made a different exporter that doesn't use javascript as a programming language, it becomes impossible to export all those games using code snippets to the new exporter, so it would make it impossible to use the new exporter for existing games. Secondly, scripting is a programming thing, and our focus is currently on the non-programming aspect.
For #2: this is a common misconception. There is no code to look at. Construct 2 does not generate code for events - it generates a data model that is then interpreted. So you can look at what Construct 2 generates for events, but it's just a big block of data. Here's a small snippet of what Space Blaster's looks like without minification enabled (which deliberately makes the code unreadable):
"Game events", [
[
1, "Score", 0, 0],
[
1, "Rockets", 0, 3],
[
0, [true, "Player and general"],
[
?[-1, cr.system_object.prototype.cnds.IsGroupActive,
?null, false, false, false, false, [
[
1, [
2, "Player and general"]]
?]]
],
[],
[
?[
?0, null, [
[-1, cr.system_object.prototype.cnds.OnLayoutStart,
null, true, false, false, false]
?],
[
[
11, cr.plugins_.Sprite.prototype.acts.Destroy, null],
[
31, cr.plugins_.Audio.prototype.acts.Play, null, [
??[
??2, ["squaremotif1", false]],
??[
??1, [
??2, ""]]
]],
[-1, cr.system_object.prototype.acts.Wait, null, [
??[
??0, [
??1, 1]]
]],
[
31, cr.plugins_.Audio.prototype.acts.Play, null, [
??[
??2, ["mattoglseby - 3", true]],
??[
??1, [
??2, "music"]]
]]
So I'm not sure you really want to do anything with that. From there C2 does call actual javascript functions which each plugin defines (@rexrainbow was describing this) but those are the code "inside" each condition and action and expression. If you like you can use Chrome's debugger and set breakpoints in these functions, but I still don't think there's much to gain from it - it tells you more about how each function works than what your events are doing overall.