Tracking: Add an official spec for the app

[evan-forbes]

While archived, the specs contain a lot of really important and critical designs that are effectively cannon. We should move as much as we can over from them, while refactoring, modifying, and updating to match the current implementation.

some special love is needed for our the encoding section, as its much more difficult to decipher the share splitting/merging implementation

• [ ] #431
• [ ] #688
• [ ] #727
• [ ] #728
• [ ] #729
• [ ] #730
• [ ] #731
• [ ] #732
• [x] #733
• [ ] #734
• [ ] #735
• [ ] #736
• [ ] #737
• [ ] #738
• [ ] #739
• [ ] #743
• [ ] #751
• [ ] #784
• [x] #792
• [ ] #795
• [x] https://github.com/celestiaorg/celestia-core/issues/866

[rootulp]

One alternative approach is to unarchive the specs repo and remove the outdated specs.

[adlerjohn]

Per-repo specs will be easier to maintain, as each team can update spec in tandem with implementation changes.

[evan-forbes]

I'm going to use this comment to continually add reminders as I think of them. Others should feel free to edit this comment or post their own comment as well.

we introduced a new validity rule here for MsgPayForData and MsgWirePayForData. https://github.com/celestiaorg/celestia-app/pull/666

[rootulp]

Relevant: https://github.com/celestiaorg/celestia-app/issues/727

[evan-forbes]

nice!! I didn't see that

[adlerjohn]

Can we turn this into a tracking issues @evan-forbes

[rootulp]

The "Pure specs" issues are blocking the merge of specs-staging into main.